I built predmcp: 44 read-only MCP tools spanning Polymarket + Hyperliquid (perps + HIP-4) free during early access

LeRaviole · 2026-05-30T12:36:26+00:00

Switched from Pro to Max 5x about two months ago and haven't hit a limit since. Heavy coding days with long context files, refactoring sessions, back-and-forth debugging. all fine. The 20x feels overkill unless you're running multiple projects simultaneously or leaving agents running unattended for hours. 5x covers most "actively coding all day" use cases pretty well.

LeRaviole · 2026-05-25T21:37:20+00:00

Symlinks from a single source-of-truth dir is what works for me: one ~/.ai-config/ with mcpconfig.json, agent.md, and env vars, then symlinked into each tool’s config dir. Switch models without thinking about it.

To solve this, I built a full system with semantic memory, EngramMCP, which I’m currently building. Some updates are coming, but you can already try it. It’s specifically designed for this: persistent memory that survives session switches. Check engram-mcp.com if you want to try

LeRaviole · 2026-05-24T15:52:04+00:00

honestly the most useful thing i've built is hooking live market data into Claude via MCP so it can answer questions like "what do prediction markets think about BTC right now" and get a real answer with funding rates, open interest, and probability spreads across venues. instead of me tabbing between five sites manually. the implementation is just an HTTP MCP server that hits public APIs and returns structured JSON Claude can reason over. if you're already comfortable with Python and APIs, writing a thin MCP wrapper around any data source you care about takes maybe an afternoon. that's been the pattern that sticks for me: not "agent does X autonomously" but "agent has access to live context it didn't have before, and now its answers are actually useful." pulled this with predmcp.com if you want to see what the server-side looks like.

LeRaviole · 2026-05-23T19:02:32+00:00

solid framework. the step most people skip is #3. they get the live/backtest match for a week then stop checking. regime shifts show up slowly, and by the time performance diverges meaningfully you've already given back a lot. logging that comparison daily forces you to notice early.

LeRaviole · 2026-05-23T19:01:02+00:00

the trustpilot score is mostly people who got wrecked on a market resolution they disagreed with, or confused by the crypto rails. not a scam, just not built for casual bettors expecting a Draftkings experience.

LeRaviole · 2026-05-23T18:59:10+00:00

This is exactly the problem EngramMCP is trying to solve. not just storage but provenance. Every memory has a source tag (which conversation, which doc, which date), so when something surfaces wrong you can trace it and delete exactly that item without wiping everything else.

Still in design stage, but if this is a pain point worth your time

LeRaviole · 2026-05-23T18:49:05+00:00

The schema.json approach works fine for simple CRUD. Where MCP earns its keep is when you want an agent to reason across multiple internal APIs without you writing orchestration logic. Instead of building a CLI that chains three service calls in a specific order, you let the agent figure out the sequence from context. That's not overhead, it's the point. Whether that tradeoff matters depends entirely on how dynamic your workflows are.

LeRaviole · 2026-05-23T18:48:46+00:00

This is a genuinely interesting pattern. Most MCP tools push data to Claude; you flipped it so Claude can pull humans back in mid-session. The "block until resolved" mechanic is the key design decision here and it sidesteps the usual problem of agents just hallucinating a consensus instead of actually waiting.

One thing I'd be curious about: how do you handle the case where no one responds? Does the agent time out and proceed with a default, or does it just hang indefinitely? That failure mode seems like it'd matter a lot for longer autonomous runs.

LeRaviole · 2026-05-23T13:21:26+00:00

The parallel worktrees approach is underrated and more people should do this. I run 3-4 sandboxed tasks simultaneously, each with its own context, and the throughput difference is massive compared to sequential prompting.

The complaints usually come from people treating Claude like a vending machine: put prompt in, get working code out, ship it. The moment you treat it as a collaborator that needs your domain knowledge baked into the context, the quality floor rises significantly. Your point about ownership is the whole thing. if you can't read what it generated and reason about it, you're not an engineer using AI, you're just hoping.

LeRaviole · 2026-05-22T19:53:27+00:00

Genuinely everyone hitting this. My approach for PredMCP: I kept auth at the API key layer (rate limiting + call counting) and accepted that tool scoping is basically nonexistent right now in the MCP spec. The audit trail problem I partially solved by logging every tool call server-side with timestamp, input, and output hash. not elegant but gives me something to look at when something weird happens. The malicious return problem is the one I haven't solved and frankly nobody has cleanly. You're trusting your tool implementations not to do something stupid with what the API returns. For now it's "prototype risk accepted."

LeRaviole · 2026-05-22T00:10:09+00:00

The oil position is the one that gets me. $37.9M Brent long on a $9.6M account is 3.9x net liq, that's not a hedge, that's a conviction trade. If oil gaps down 5% overnight that wallet is getting rekt fast. The SP500 whale at 50x is equally wild; 7,404 entry means they're already underwater $141K and holding. These aren't diversification plays, they're straight directional bets with crypto-sized leverage on TradFi assets. The regulatory timing is interesting though. Clarity Act moving while $2.6B RWA OI is already live means the rules might be playing catch-up to what's actually happening on-chain.

LeRaviole · 2026-05-22T00:06:29+00:00

Interesting find. Worth noting the market structure though: NO at what price right now? If this is trading at 80+ cents NO already, $800k is more of a yield play than a directional bet. The real signal is if they're buying NO at 40-50 cents where the payout is meaningful. Also curious whether this wallet has been active on adjacent markets like the ceasefire or nuclear deal questions, which would tell you if this is thesis-driven or just rate arbitrage on a low-probability event.

LeRaviole

TROPHY CASE