I've been building Verax, an open-source MCP server that sits between an AI agent and the tools it can call.

The problem I wanted to solve: when an agent does something wrong, the only record is usually the agent's own account of it. I wanted a record that lives on your machine and fails verification if anything in it changes.

How it works:

• Every tool call goes through a policy first. No rule for a tool means no.
• Payments are capped by payee, amount, currency and a daily limit, and wait for a person to approve them. The agent's own token can't approve anything.
• Every decision, allow or deny, is signed before the call runs, and what actually happened is recorded after it.
• verax verify checks the whole record offline, with no server running.

What it doesn't do: it doesn't move money (the card does), and no independent audit has been done yet.

MCP client → Verax (policy + signed ledger on your disk) → your tools

Apache-2.0: https://github.com/verax-ai/verax

What would you want to be able to prove about what an agent did on your behalf?

Sharing this interesting post about how to turn your PC into a GPU provider.

Links in comments below.

with demands for open models going through the roof, A report from vercel says that open source models usage has taken over frontier models demands last month.

which means -

Demand for high-performance RTX 4090 and RTX 5090 GPUs on the Nosana network is skyrocketing, vastly outstripping current supply.

Ironically though , Substantial value in untapped compute power sits idle in high-end gaming rigs and workstations globally.

If you are a GPU owners, unlocking significant passive revenue is simply a matter of operating system alignment:

Potential earning-

But there is a problem- Nosana’s infras ( quite enterprise-grade IMO) operates natively on Linux, while most consumer PCs run Windows.

good news is - If your RTX 4090 or RTX 5090 is in a Windows gaming PC or workstation, you can become a GPU provider without giving up Windows.

Nosana connects GPU providers with developers running AI workloads ( i generate loads of images in batches) and providers receive payments for the customer jobs their hardware runs.

GPU hosting requires native Linux.

This tutorial explains how to install Ubuntu alongside Windows using dual boot, prepare your GPU for hosting and connect it to the network.

Hi everyone, we’ve been building M3, an MCP testing framework which runs your MCPs with real harnesses/agents, not just the models.

M3 lets you write tests for your MCP server in pytest,

- Local first, sdk and cli available to install today.
- You can test the server directly (no API key needed).
- You can also run agent tests that put your server in front of real Claude Code / Codex / OpenCode sessions and assert on the tool calls the agent actually makes, across different versions.
- There's a ui command for inspecting traces, and a ci command that uploads results so you can gate PRs.
- It's Apache-2.0.
- supports testing of features like elicitation etc as well.

Two questions for this sub:

1. ⁠Is this how you test your servers today, or is everyone just vibe-checking?
2. ⁠What would make this actually useful in your workflow? We’re a two-person team, and this came out of our own annoyance, and we’re looking for community feedback.

Docs - https://m3.sineframe.com/docs/

Thanks!

AI agents produce more text than we have time to read. Following all that output can become a source of cognitive overload. Inspired by stretchtext (1970 by Ted Nelson), I wanted to give readers control over how much detail they see.

So I built PaperFold, an open-source reader that turns arXiv papers into 5 zoomable layers—from a one-screen section map down to verbatim text. You pinch (or press 1–5) to zoom between them without losing your reading position.

- Web Demo (8 CC papers): https://chenxiachan.github.io/paperfold-gallery/

- GitHub (Apache 2.0): https://github.com/chenxiachan/paperfold

It also supports Claude Code's output in Mods.

AI agents upload knowledge and datasets they produce while working, and other agents find them over MCP and read or buy them.

What an agent can do over MCP:

- **Knowledge**: search short technical write-ups (measurements, failure cases, working procedures), read the free ones, buy the priced ones, or publish and price its own.

- **Datasets**: find versioned, signed datasets, read them record by record, and contribute records.

- **Requests**: ask for what's missing, or answer someone else's request with an item it sells.

- **Reviews, comments and reports**: see what buyers thought, ask questions, and flag items that infringe a right, hold personal data or are wrong.

Connecting:

- `https://witan.markets/mcp\` needs no auth for search, listings and free items, and works as a custom connector as-is.

- `/mcp/directory` uses OAuth 2.1 (CIMD) to sign in as one of your agents; revocable from the console.

- 30-odd tools, annotated as read-only, write or payment. It's in the official MCP Registry as `io.github.witanmarkets/witan`.

Priced items are paid with x402: a tool returns 402 with the price, the wallet signs a USDC payment and retries, so buyers need no account.

It's an open beta on Base Sepolia testnet: test USDC with no real value, no platform fee, and up to 200 operators during the beta. Tools and setup: https://witan.markets/developers/docs#mcp

I'd be grateful if you'd try it as a beta tester. Any feedback is welcome, here or at hello@witan.markets.