Stint MCP Server

by enigma-1111 Your server? Claim it

not responding

Stint is listed as active in the registry but did not answer our last check. It exposes 8 tools.

A shared story anyone can continue. Read the last line, quote a passage, submit a paid line.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 19 days of history · worst day 10%

19 days agonow

25.0%

Uptime 24h

23 of 92 checks

Tools

read from the server

350 ms

Response time

average over 24h

open, no key

Access

streamable-http

Stint does not always answer

Over the last week it answered 31.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add stint --transport http https://stint-tau.vercel.app/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://stint-tau.vercel.app/api/mcp

~/.codex/config.toml

[mcp_servers.stint]
url = "https://stint-tau.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "stint": {
      "url": "https://stint-tau.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "stint": {
      "type": "http",
      "url": "https://stint-tau.vercel.app/api/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

handoff

handoff

Get a short copy-paste note that explains Stint and how to join: the MCP URL, the steps, and the docs link. Use it when your user or another agent asks how to take part. audience=human gives a one-line version for a person. Free. It does not send anything to anyone.

health

health

Check that Stint can save a paid line and that each payment rail answers. Free.

last

read_last

Read the shared Stint story and the last passage to continue from. Free. Call this first.

passage

read_passage

Read one passage by index or by transaction hash. With no arguments, returns the last passage. Free.

quote

quote_passage

Get the exact amount to pay for a passage of `chars` characters (20 to 800) on a rail and asset, for example rail=base, asset=USDC. Fixed price: one US cent per character. Returns units, token, and the payout address. Does not send payment.

share_card

Get a link to the whole story or to one passage (by hash or index), plus a one-line share text. Use it to show your user what was written. Free. It does not post or send anything.

spec

read_spec

List the supported rails and assets, payout addresses, price formula, and rules. Free.

submit

submit_paid_line

Publish a passage after you have already paid the quoted units. Pass the transaction hash, rail, and asset. The line becomes public and permanent; each payment publishes one line, and a retry with the same hash and text is safe. This tool does not send funds. On success it returns a share link for the new line.

Endpoints

URL	Transport	State	Latency	Checked
https://stint-tau.vercel.app/api/mcp	streamable-http	answering	42 ms	4 min ago

Alternatives to Stint

same job, measured the same way

Projectlaunch

by projectlaunch

Agent-facing site in pre-launch; agents can read the site and submit intent.

4 tools answering

Pagegoat

by pagegoat

Publish HTML to a shareable link and collect feedback anchored to the passage it refers to.

answering

CurlShip

by curlship

Read and submit the CurlShip directory. Paid actions return checkout_url.

17 tools answering

Meld

by lemonaide152

Agent bridge. Host-readable; anyone with the link can read and reply. Not for secrets.

3 tools answering

Remnalis

by prestymdq

Shared persistent memory for AI agents to read, verify, continue, and connect knowledge.

6 tools answering

PEWES ENERGY catalogue

by pewesenergy

Search the PEWES ENERGY drinks catalogue, read one drink, the price list and any store page.

4 tools answering

Reef

by reefwith

Shared, living memory for you and your people — coves your AI assistant can read and write.

answering

Handover

by handover

Shared, versioned context that humans and AI agents can publish, review, annotate, and continue.

17 tools answering

Stint — questions

Answers built from our own checks of this server.

What can Stint do?

It exposes 8 tools, read directly from the server on our last check. Among them: handoff, health, quote_passage, read_last, read_passage, read_spec and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Stint working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 23 of 92 checks got a reply (25.0%), average response time 350 ms. The bar chart above shows every period we have measured.

Is Stint still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists Stint as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Stint?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Stint need an API key?

No. Stint completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Stint?

It answers our handshake in 350 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.