Locus MCP server
online · 100% uptimecom.paywithlocus/locus·v0.3.37Pay-per-use APIs for agents: web research, data lookups, and metered endpoints billed to credits.
0 stars
Reviews
Write oneNobody has reviewed Locus yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Locus tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 356ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 3 days ago15/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
How Locus compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 97/100
- higher than 98% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 219 ms
- faster than 60% of 30,031 servers
Release history: 3 versions in the registry since 2026-09-17, latest 2026-09-22, typically one every 4 days.
Install Locus in Claude Code, Cursor or VS Code
claude mcp add --transport http locus https://api.paywithlocus.com/api/credits/mcp
What the publisher says
From the Locus repository's README, as published. We do not edit it. Read it on GitHub
Locus plugin
Pay-per-use APIs for coding agents. This plugin connects the Locus MCP server and teaches your agent how to use it well: cited web research, paid data and API lookups, and thousands of metered provider endpoints billed to one prepaid workspace credit balance.
One repo, one plugin, many agents. The same plugin installs into Claude Code, Codex, Cursor, Grok, OpenClaw, and any client that speaks the Agent Plugins or Agent Skills open standards.
What you get
(streamable HTTP). Sign-in is OAuth with browser consent; no keys are stored in configuration.
- MCP server connection to https://api.paywithlocus.com/api/credits/mcp
routing, cost quotes, idempotent billing, error recovery, and spend safety.
- The locus skill: operating instructions for the agent covering tool
it. Human sign-up through the OAuth page is the default. Agent-owned accounts via AgentID exist for headless runtimes, and only they get agent-driven capability selection and a user-requested Stripe funding handoff; human-owned accounts manage both in the dashboard.
- The locus-setup skill: onboarding when the user asks the agent to do
bounded pilots, immutable versions, and durable run recovery through the same authorized connection.
- The locus-workflows skill: safe hosted Workflow authoring, fixtures,
No account yet? Authenticate the server and create the account on the OAuth sign-in page that opens; that is the whole flow for a person with a browser. Tools are enabled and credits added in the dashboard at platform.paywithlocus.com.
Install
Claude Code
/plugin marketplace add locus-technologies/locus-pro-plugin
/plugin install locus@locusThen run /mcp, select locus, and authenticate.
Already added the server manually as locus-pro via claude mcp add? Remove
it first (claude mcp remove locus-pro) so you don't carry two connections
to the same server.
Codex
codex plugin marketplace add locus-technologies/locus-pro-plugin
codex plugin add locus@locus
codex mcp login locusHermes
hermes plugins install locus
hermes plugins enable locus
hermes mcp login agent-plugin-locus-0b597595__locusComplete browser OAuth, then start a new Hermes session. The plugin includes the usage, setup, and Workflow skills; no separate skill install is needed.
Cline
cline mcp install locus --transport http \
https://api.paywithlocus.com/api/credits/mcpKeep Remote (HTTP), choose OAuth, leave the client ID blank for dynamic registration, and complete sign-in in the browser. No clone, build, API key, or environment variable is required.
Cursor
Add the MCP server directly in ~/.cursor/mcp.json:
{
"mcpServers": {
"locus": {
"url": "https://api.paywithlocus.com/api/credits/mcp",
"headers": { "X-Source-Name": "cursor-plugin" }
}
}
}Cursor's OAuth flow completes in the browser on first use. Once the Locus listing clears Cursor Marketplace review, you will also be able to install it from Customize → Plugins (search "Locus") or with /add-plugin locus in chat.
Grok
grok plugin install locus-technologies/locus-pro-plugin --trustGrok requires explicit trust to install plugins (they can run MCP servers and skills); review the repo, then pass --trust. Grok discovers the server's OAuth automatically and opens the browser flow on first use.
OpenClaw
Install the plugin from this repo as a marketplace source; the bundle already maps the MCP server, so no manual server configuration is needed:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Locus: common questions
- Is Locus MCP server safe?
- Yes, by our scan: it is graded A (97/100). Read the Locus safety report
- How do I install Locus?
- It runs remotely at api.paywithlocus.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Locus need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Locus maintained?
- The last commit was 36 days ago (2026-09-29). The latest release is v0.3.37.
- Is Locus up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Locus compare with other MCP servers?
- safety score 97/100 (higher than 98% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 219 ms (faster than 60% of 30,031 servers). Full comparison.