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

agent-decision-engine

https://decide.memoryapi.org

Registry code: 7c0239b7e101a7b0

api record

Vendor trust score (composite: reviews, uptime, SLA)

from a public catalogue that lists it, not from the operator

endpoint
https://decide.memoryapi.org/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 agent-decision-engine live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is agent-decision-engine free to use?
Not measured yet.
What tools does agent-decision-engine have?
6 tools: report_outcome, compare, recommend, predict, alternatives, trust_score.
Is agent-decision-engine 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%

90 days 99.3%· all time 99.3%

latency
427ms

last good check

priced tools
1

of 6 tools

_ answered our checks, 90 days 437 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
  • get a trust score for an api vendor
  • compare api vendors
  • find alternatives to a vendor
  • recommend a vendor for a need
  • report a vendor call outcome
takes → gives
text → data
tools
5 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 15 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
18

distinct

settlements
35

last 2026-11-09

received on chain
0.175 USDC

shared-payto, undercounted

_ what it can do 6 tools
1 paid 5 never probed 1 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.

  • trust_score reads 0.01 USDC paid never probed

    Get composite trust score for a vendor. Returns reliability, predicted success rate, GitHub/npm/uptime signals.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "vendor"
      ],
      "properties": {
        "vendor": {
          "type": "string",
          "description": "Vendor domain e.g. stripe.com, openai.com"
        }
      }
    }
    arguments 13 lines
  • report_outcome changes data unknown never probed

    Report a transaction outcome to improve future predictions. Free — contributes to the shared trust dataset.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "vendor",
        "success"
      ],
      "properties": {
        "action": {
          "type": "string",
          "description": "Action type"
        },
        "vendor": {
          "type": "string",
          "description": "Vendor domain"
        },
        "success": {
          "type": "boolean",
          "description": "Whether the transaction succeeded"
        },
        "agent_id": {
          "type": "string"
        },
        "cost_usd": {
          "type": "number"
        },
        "latency_ms": {
          "type": "number"
        }
      }
    }
    arguments 31 lines
  • compare reads unknown never probed

    Head-to-head comparison of multiple vendors. Returns ranked list with trust scores, reliability, and success rates.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "vendors"
      ],
      "properties": {
        "vendors": {
          "type": "string",
          "description": "Comma-separated vendor list e.g. openai.com,anthropic.com,groq.com"
        }
      }
    }
    arguments 13 lines
  • recommend reads unknown never probed

    Find the best vendor for a stated need. Categories: weather-api, llm-api, payment-api, email-api, search-api, database, vector-db, object-storage, maps-api, sms-api, auth, monitoring, cdn, transcription.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "need"
      ],
      "properties": {
        "need": {
          "type": "string",
          "description": "What you need, e.g. \"weather api\" or \"llm api\""
        },
        "limit": {
          "type": "number",
          "description": "Number of results (default 3)"
        },
        "budget": {
          "type": "number",
          "description": "Monthly budget in USD"
        }
      }
    }
    arguments 21 lines
  • predict reads unknown never probed

    Predict success probability for a specific vendor action. Uses historical outcome telemetry when available.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "vendor"
      ],
      "properties": {
        "action": {
          "type": "string",
          "description": "Action type e.g. payment, api-call, webhook"
        },
        "vendor": {
          "type": "string",
          "description": "Vendor domain"
        }
      }
    }
    arguments 17 lines
  • alternatives reads unknown never probed

    Find ranked alternatives to a given vendor in the same category.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "vendor"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "description": "Max results (default 4)"
        },
        "vendor": {
          "type": "string",
          "description": "Vendor to find alternatives for"
        }
      }
    }
    arguments 17 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 7c0239b7e101a7b0.

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

_ also on memoryapi.org 24 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

16 more sit on this domain. All of them.