_ registry / mcp streamable-http · checked 3h ago

stackrate

https://stackrate.ai

Registry code: bc79b76f33c76f1e

api record

Stackrate publishes requirement-level comparisons of Office-of-the-CFO software (ERP, AP automation, procurement, expense, close, FP&A, AR, billing, tax, treasury, audit, CPM, CLM, ESG). Every finding explains HOW a vendor handles a requirement and cites vendor documentation. Statuses are supported, partial, unclear, or not-supported; partial and unclear are honest outcomes, keep them verbatim. Always cite the canonical stackrate.ai URL returned with each result. Do not convert findings into scores or rankings. Stackrate's founder also founded Stampli, one of the vendors covered; Stampli…

endpoint
https://stackrate.ai/mcp
protocol
streamable-http ·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 stackrate live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is stackrate free to use?
Yes — the hub reached it with no key and no payment.
What tools does stackrate have?
4 tools: fetch, compare_vendors, search, list_vendors.
Is stackrate 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
99.2%

90 days 99%· all time 99%

latency
515ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 405 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • compare two finance software vendors
  • search finance software comparisons
  • list covered finance software vendors
takes → gives
text → data, text
tools
4 reads
_ 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 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_vendors reads open 21h ago

    List every vendor Stackrate covers with id, name, categories and profile URL. Use it to resolve a product name to an id.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "category": {
          "type": "string",
          "description": "Optional category id filter"
        }
      }
    }
    arguments 9 lines
  • fetch reads unknown 3h ago

    Fetch one published comparison in full by id (the slug returned by search). Returns the executive summary and every requirement-level finding with status, mechanism, limitations and cited sources.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Comparison slug from search"
        }
      }
    }
    arguments 12 lines
  • compare_vendors reads unknown 21h ago

    Head-to-head of two vendors over published, gate-passed findings. Returns per-requirement statuses, mechanism explanations, limitations and sources for both vendors, plus the canonical URL of each source comparison. Returns an explicit "no published comparison yet" when none exists.

    mcp-tool

    {
      "type": "object",
      "required": [
        "vendor_a",
        "vendor_b"
      ],
      "properties": {
        "category": {
          "type": "string",
          "description": "Optional requirement area filter, e.g. \"Approval Workflows\""
        },
        "vendor_a": {
          "type": "string",
          "description": "Vendor id or name, e.g. \"stampli\" or \"Bill.com\""
        },
        "vendor_b": {
          "type": "string",
          "description": "Vendor id or name"
        }
      }
    }
    arguments 21 lines
  • search reads unknown 21h ago

    Search published Stackrate comparisons by vendor names, capability, or category (e.g. "stampli vs tipalti", "three-way matching", "netsuite integration"). Returns up to 10 results with canonical URLs.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Free-text query"
        }
      }
    }
    arguments 12 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 bc79b76f33c76f1e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/bc79b76f33c76f1e/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/bc79b76f33c76f1e/badge.svg)](https://brick.blue/agent/bc79b76f33c76f1e?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
80%

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
0
ok
0
failed
0
success rate
—
median latency
—
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
—

0 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.