AI builder & learner | Building awesome stuff + documenting journey to first successful application| DMs open for collabs/advice. Building @Glintbase.

Joined June 2024
If you're in Crypto, pivot to AI.
If you're in AI, pivot to crypto.
1
42
Having an llms.txt doesn't make you agent-ready. Most readiness checks stop at "does the file exist?" Ours asks whether it works. Here's how the Glintbase score (ARS 3.2) is built 🧵
1
1
106
6/ The part most founders skip: ARS is not validated as a predictor of agent success. No study yet links the score to real agent outcomes. Read it as "readiness signals present and verified," not "agents will succeed." Closing that gap is the actual research.
1
19
7/ Full methodology, all 129 checks, and the scanner are open source. Scan your own site and tell me which check you think is wrong. Methodology: glintbase.dev/methodology Blog:glintbase.dev/blog/ars-3-2-e… Scanner: scan.glintbase.dev
13
Elon musk did all of this in one lifetime! No one even comes close.
1
15
446
Seriously how do you founders carry out B2B sales? I've been trying for a while but it seems I'm doing something wrong. Can I get some guidance pls?
1
32
It's actually cause @e2b is agent ready. I recently ran a study where I benchmarked sandbox providers for agent readiness and E2b was far the easiest for agents to integrate costing far less tokens and number of steps. Great work from the team optimising their Infra for AI Agents xitter.cf/Connex01/status/210785…
61% of traffic on @e2b is agents. Agents are already the biggest users of E2B. Soon they'll be also assembling their own infrastructure they need for every task.
2
50
We asked 1,773 remote MCP servers to call a tool that doesn't exist. 272 said it worked. HTTP 200, no error signal. Your agent can't tell the difference either. Full thread 👇 @dsp_ @RhysSullivan
Yesterday we probed 3,000 remote endpoints from the official MCP Registry (frame: 26,365). 56.9% completed a handshake and listed tools anonymously. 29.3% need auth. Pre-registered, with intervals on every figure 🧵
2
1
51
Yesterday we probed 3,000 remote endpoints from the official MCP Registry (frame: 26,365). 56.9% completed a handshake and listed tools anonymously. 29.3% need auth. Pre-registered, with intervals on every figure 🧵
1
1
1
3
187
6/ What we got wrong is in the report too: • our own pre-registered era-detection rule misread 404/-32601, so we re-ran both rounds • another crawl overlapped one round, so we discarded it • our re-probing used up one gateway's free quota All three are logged as deviations.
1
17
7/ 99.6% re-probe agreement, excluding that gateway. Wilson 95% intervals, host-weighted shares. The harness and per-endpoint data are public. Full report: glintbase.dev/research/remot…
19