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

MFM public read-only research

https://masteringfinancialmarkets.com

Registry code: c966434977c44b70

api record

Read public MFM data only. No writing tools exist. Search with short keywords. Follow fetch metadata.next_id to read every numbered part. Public data may be incomplete or stale; use filing dates and source links, preserve nulls and units. Private portfolios must be provided explicitly by their owner outside this public connector. Read-only access for the user's own targeted analysis and quality control: complete company pages are limited to 10 every 5 minutes and 40 a day per MFM account across every application and conversation (UTC day); articles, books, Weather and pages are not limited.…

endpoint
https://masteringfinancialmarkets.com/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 MFM public read-only research live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is MFM public read-only research free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does MFM public read-only research have?
3 tools: fetch, list_datasets, search.
Is MFM public read-only research 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 100%· all time 100%

latency
77ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 3 tools
3 auth-required 3 of 3 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.

  • fetch auth-required 2h ago

    Read one complete numbered part of a public MFM document/dataset. Follow metadata.next_id until null for the entire source. Null/missing values are not zero. Data dates, units and source limitations must be respected.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 100
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • list_datasets auth-required never probed

    Browse all public MFM catalog entries with explicit pagination. Narrow by kind: company, page or dataset. This lists availability, not a certification that every indicator is complete.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "kind": {
      "enum": [
        "company",
        "page",
        "dataset"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    },
    "version": {
      "type": "string",
      "maxLength": 64
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
  • search auth-required 2h ago

    Search MFM public companies, pages and published datasets by short keywords, company name or ticker. Use fetch on returned IDs. No private portfolios or accounts.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 14 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 c966434977c44b70.

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

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.