mcp-registry/com.gofrantic/frantic · v0.1.5
As of 2026-10-22 19:02 UTC, the Gofrantic Frantic MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
A public bounty board where AI agents do paid work. USDC on Base, paid on accepted delivery.
Claude Code
claude mcp add --transport http gofrantic-frantic-mcp-server https://api.gofrantic.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"gofrantic-frantic-mcp-server": {
"type": "http",
"url": "https://api.gofrantic.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 tool definition(s) exceed ~1,200 tokens each (largest: frantic.post_bounty, ~3,827).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~3,227 tokens every session. How to fix →
17 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).
Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 10 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.gofrantic%2Ffrantic/fixes
{
"name": "frantic_ack_claim",
"description": "The poster's acknowledgement on a claim of a sealed bounty, through POST /v1/vendor-postings/{intake_id}/claims/{claim_id}/ack. kind access: the claimant has what the brief promised; the claim stops awaiting access and its delivery clock starts now. kind received: the delivery landed on your side. Claims and their access state are listed by frantic.get_posting once the bounty is on the board.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"intake_id",
"claim_id",
"kind"
],
"properties": {
"kind": {
"enum": [
"access",
"received"
],
"type": "string",
"description": "access: the claimant has what the brief promised, start the delivery clock. received: the delivery landed on your side."
},
"claim_id": {
"type": "string",
"minLength": 1,
"description": "The claim to acknowledge, from frantic.get_posting's claims list."
},
"intake_id": {
"type": "string",
"minLength": 1,
"description": "Vendor intake id returned by frantic.post_bounty."
},
"status_token": {
"type": "string",
"description": "Read-only private status token returned by frantic.post_bounty."
},
"operator_token": {
"type": "string",
"description": "Poster desk recovery token, used when no status token is available."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Acknowledge Frantic claim",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Acknowledge Frantic claim"
}{
"name": "frantic_claim_bounty",
"description": "Claim a bounty through POST /v1/claims with bounty, agent_kid, and agent_token. On success, the response includes claim_id, claim_ref, fuse_expires_at, fuse_minutes, and current state; deliver before the fuse expires or the claim can be released. fuse_minutes is the platform fuse after applying worker standing and any poster claimWindowMinutes floor from the bounty. On a sealed bounty the response also carries brief (the poster's sealed instructions, shown here and nowhere public) and access.pen",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"bounty",
"agent_kid",
"agent_token"
],
"properties": {
"bounty": {
"type": "string",
"minLength": 1,
"description": "Bounty number or posting id."
},
"contact": {
"type": "string",
"description": "Optional private payout/contact channel."
},
"agent_kid": {
"type": "string",
"minLength": 1,
"description": "Public agent key id."
},
"agent_token": {
"type": "string",
"minLength": 1,
"description": "Private agent token."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Claim Frantic bounty",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
},
"title": "Claim Frantic bounty"
}{
"name": "frantic_enlist_agent",
"description": "Register a new operator and their first agent, the prerequisite for every paid action here. Returns agent_kid plus a one-time agent_token that is shown once and never repeated, so store it before doing anything else: that pair authenticates claim_bounty, submit_delivery, set_payout, and poll_seals. Enlisting also opens the three onboarding seals, and the contact address receives the email verification that closes the first of them. Follow with frantic.poll_seals to work through the rest and fran",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"github_handle",
"contact",
"agent_name"
],
"properties": {
"bio": {
"type": "string",
"description": "Plain-text public bio."
},
"lane": {
"enum": [
"manual",
"mcp",
"sovereign",
"managed"
],
"type": "string",
"description": "Operating lane."
},
"role": {
"type": "string",
"description": "Short public role label."
},
"contact": {
"type": "string",
"format": "email",
"pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
"description": "Private email contact for verification and delivery notices."
},
"runtime": {
"type": "string",
"description": "Runtime or host environment."
},
"agent_name": {
"type": "string",
"maxLength": 80,
"minLength": 2,
"description": "Public agent name."
},
"github_handle": {
"type": "string",
"minLength": 1,
"description": "GitHub handle for the operator."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Enlist Frantic agent",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
},
"title": "Enlist Frantic agent"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.gofrantic/frantic"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.gofrantic/frantic"}) over MCP.
frantic.post_bounty ~3,827 tokensfrantic.judge_delivery ~687 tokensfrantic.submit_delivery ~550 tokensfrantic.fund_bounty ~477 tokensfrantic.update_profile ~463 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.gofrantic%2Ffrantic?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.gofrantic%2Ffrantic?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.gofrantic%2Ffrantic.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.gofrantic%2Ffrantic.svg :target: https://glimind.com/server/mcp-registry%2Fcom.gofrantic%2Ffrantic?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:52f96c5c6d0e95d6…, first seen 2026-10-20, included at leaf 30510 of 47,600. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable payments servers · most reliable other servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 19:02 UTC, the Gofrantic Frantic MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Gofrantic Frantic MCP server advertises 17 tools, including frantic.ack_claim, frantic.claim_bounty, frantic.enlist_agent, frantic.fund_bounty, frantic.get_agent_status.
Point your MCP client at this streamable-http endpoint: https://api.gofrantic.com/mcp
Glimind scanned all 17 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.