_ registry / mcp http-sse · checked 2h ago

SettleGrid

https://settlegrid.ai

Registry code: 5b7ef6de781cd93d

api record

Browse and search the SettleGrid marketplace of paid AI tools, view pricing and developer profiles, and invoke a listed tool by its slug.

endpoint
https://settlegrid.ai/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is SettleGrid live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is SettleGrid free to use?
Yes — the hub reached it with no key and no payment.
What tools does SettleGrid have?
6 tools: get_developer, get_tool, call_tool, list_marketplace_tools, search_tools, list_categories.
Is SettleGrid safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.5%· all time 99.5%

latency
612ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 377 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search a marketplace of paid ai tools
  • get tool pricing and developer details
  • invoke a marketplace tool by slug
takes → gives
text, data → data
tools
5 reads1 effect unclear
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
3 open 3 never probed 3 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_marketplace_tools reads open 24h ago

    Browse the most popular tools on the SettleGrid marketplace with pricing and availability info. Each result includes cost-per-call, total invocations, and whether the tool requires an API key. Optionally filter by category. Use this to find callable tools before invoking them with call_tool.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "number",
          "default": 20,
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum number of tools to return (1-50, default 20)"
        },
        "category": {
          "type": "string",
          "description": "Filter by category slug (e.g. \"data\", \"nlp\", \"search\", \"finance\")"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • search_tools reads open 24h ago

    Search the SettleGrid marketplace for AI tools by keyword, category, price, or rating. The catalog grows daily through auto-indexing from npm, HuggingFace, Smithery, and other registries. Returns tool names, slugs, descriptions, pricing, and developer info. Use this as your starting point to find tools for any task.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "number",
          "default": 20,
          "maximum": 100,
          "minimum": 1,
          "description": "Maximum number of results to return (1-100, default 20)"
        },
        "query": {
          "type": "string",
          "description": "Free-text search query (e.g. \"weather\", \"translate\", \"sentiment\")"
        },
        "category": {
          "type": "string",
          "description": "Filter by category slug (e.g. \"data\", \"nlp\", \"finance\"). Use list_categories to see all options."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • list_categories reads open 24h ago

    List all available tool categories on the SettleGrid marketplace with the number of tools in each. Use this to understand what types of tools are available before searching.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_developer reads unknown 20h ago

    Get a developer's public profile, bio, reputation score, and their published tools on SettleGrid. Useful for evaluating tool quality by checking the developer's track record.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 128,
          "minLength": 1,
          "description": "The developer's unique profile slug (returned by search_tools and get_tool)"
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • get_tool reads unknown 20h ago

    Retrieve full details for a specific tool by its slug, including description, pricing breakdown, developer info, recent reviews, changelog history, and quick-start code snippets. Use after search_tools to get deeper information before deciding to invoke a tool.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 128,
          "minLength": 1,
          "description": "The unique slug of the tool (e.g. \"wikipedia\", \"forex-rates\", \"dad-jokes\")"
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • call_tool unknown never probed

    Invoke any tool on the SettleGrid marketplace by its slug. Pass arguments as a JSON object. Free showcase tools work without an API key. Paid tools route through the Smart Proxy and require an API key (passed via the x-api-key header on the MCP connection). Use search_tools or list_marketplace_tools first to find the right tool and its slug.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "args": {
          "type": "object",
          "description": "Arguments to pass to the tool as a JSON object (e.g. { \"query\": \"Einstein\" })",
          "additionalProperties": {}
        },
        "slug": {
          "type": "string",
          "pattern": "^[a-z0-9][a-z0-9._-]{0,127}$",
          "maxLength": 128,
          "minLength": 1,
          "description": "Tool slug (e.g. \"wikipedia\", \"dad-jokes\", \"forex-rates\")"
        },
        "method": {
          "type": "string",
          "maxLength": 64,
          "description": "Specific method or action to call on the tool (e.g. \"search\", \"get_random\")"
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5b7ef6de781cd93d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5b7ef6de781cd93d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5b7ef6de781cd93d/badge.svg)](https://brick.blue/agent/5b7ef6de781cd93d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
1,132ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.