mcpbeat Sign in

Locus MCP Server

by paywithlocus Your server? Claim it
answering

Locus is answering right now. Last checked 3 min ago. Last commit 17 Sep 2026.

Pay-per-use APIs for agents: web research, data lookups, and metered endpoints billed to credits.

Uptime history 17 days of history
17 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
822 ms
Response time
average over 24h
0
Stars
last commit 17 Sep 2026

Nothing serious here today

Today is the operative word: we check Locus every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add locus --transport http https://api.paywithlocus.com/api/credits/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "locus": {
      "url": "https://api.paywithlocus.com/api/credits/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.locus]
url = "https://api.paywithlocus.com/api/credits/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "locus": {
      "url": "https://api.paywithlocus.com/api/credits/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "locus": {
      "url": "https://api.paywithlocus.com/api/credits/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.paywithlocus.com/api/credits/mcp streamable-http sign-in 856 ms 3 min ago

Alternatives to Locus

same job, measured the same way
Reddit data for agents
by fetcher-reddit

15 Reddit endpoints. Pay per call in USDC via x402.

17 tools answering
Blockrun MCP
by blockrunai

Web search, deep research, prediction markets & crypto data for AI agents. Pay per call via x402.

554 installs/wk local only
Google Search data for agents
by fetcher-google

1 Google Search endpoints. Pay per call in USDC via x402.

3 tools answering
Delx Commerce — Pay-per-Result APIs for Agents
by davidmosiah

1005 pay-per-result MCP/x402 APIs for web, data, Base, reliability and agent delivery.

1068 tools answering
Twitter / X data for agents
by fetcher-twitter

15 Twitter / X endpoints. Pay per call in USDC via x402.

17 tools answering
C
Forage
by forage

Web search and URL-to-markdown for agents. Pay per call in USDC on Base, no signup.

2 tools answering
Google Maps data for agents
by fetcher-google-maps

4 Google Maps endpoints. Pay per call in USDC via x402.

6 tools answering
TikTok data for agents
by fetcher-tiktok

13 TikTok endpoints. Pay per call in USDC via x402.

15 tools answering

Locus — questions

Answers built from our own checks of this server.

Why is there no tool list for Locus?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Locus working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 822 ms. The bar chart above shows every period we have measured.
How do I connect Locus?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Locus?
No API key is involved. Locus answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Locus?
It answers our handshake in 822 ms on average, which is faster than 13% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Locus open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.