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

MDataAccess

https://api.mdataaccess.com

Registry code: 57b5c7cc749d3037

api record

MDataAccess provides paid business, people, lead, company, and web data. These MCP tools prepare the exact paid API request; they do not return paid data and never bypass x402. Follow the returned URL, complete the x402 USDC payment on Base, and use the paid API response.

endpoint
https://api.mdataaccess.com/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 MDataAccess live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is MDataAccess free to use?
Yes — the hub reached it with no key and no payment.
What tools does MDataAccess have?
7 tools: enrich_person, find_decision_maker, find_lead, search_companies, enrich_company, read_webpage, search_people.
Is MDataAccess 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.4%

90 days 98.8%· all time 98.8%

latency
180ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 334 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
productivity & business crm & sales
used for
  • enrich a company by domain
  • enrich a person by email or linkedin
  • find a decision-maker at a company
  • find a sales lead
takes → gives
text → data
tools
7 reads
note
resells another provider
_ 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 stands behind 3 doors on this origin, so the chain figures are the operator's. 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
2

distinct

settlements
3

last 2026-10-30

received on chain
0.006 USDC

counted from three payers (thin, concentrated)

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 7 tools
7 never probed 0 of 7 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.

  • enrich_person reads unknown never probed

    Prepare a paid person enrichment request when an email, LinkedIn URL, or name is known.

    mcp-tool

    {
  "type": "object",
  "title": "enrich_personArguments",
  "properties": {
    "name": {
      "type": "string",
      "title": "Name",
      "default": ""
    },
    "email": {
      "type": "string",
      "title": "Email",
      "default": ""
    },
    "company": {
      "type": "string",
      "title": "Company",
      "default": ""
    },
    "linkedin_url": {
      "type": "string",
      "title": "Linkedin Url",
      "default": ""
    }
  }
}
    arguments 26 lines
  • find_decision_maker reads unknown 21h ago

    Prepare a paid request for one senior decision-maker at a known company and function.

    mcp-tool

    {
  "type": "object",
  "title": "find_decision_makerArguments",
  "required": [
    "company",
    "function"
  ],
  "properties": {
    "company": {
      "type": "string",
      "title": "Company"
    },
    "function": {
      "type": "string",
      "title": "Function"
    }
  }
}
    arguments 18 lines
  • find_lead reads unknown 21h ago

    Prepare a paid request for one compact sales-ready lead at a known company and function.

    mcp-tool

    {
  "type": "object",
  "title": "find_leadArguments",
  "required": [
    "company",
    "function"
  ],
  "properties": {
    "company": {
      "type": "string",
      "title": "Company"
    },
    "function": {
      "type": "string",
      "title": "Function"
    }
  }
}
    arguments 18 lines
  • search_companies reads unknown 3h ago

    Prepare a paid PDL SQL company-search request. Exactly one company is returned by the API.

    mcp-tool

    {
  "type": "object",
  "title": "search_companiesArguments",
  "required": [
    "sql"
  ],
  "properties": {
    "sql": {
      "type": "string",
      "title": "Sql"
    }
  }
}
    arguments 13 lines
  • enrich_company reads unknown never probed

    Prepare a paid company enrichment request when a company name or domain is known.

    mcp-tool

    {
  "type": "object",
  "title": "enrich_companyArguments",
  "properties": {
    "name": {
      "type": "string",
      "title": "Name",
      "default": ""
    },
    "website": {
      "type": "string",
      "title": "Website",
      "default": ""
    }
  }
}
    arguments 16 lines
  • read_webpage reads unknown 21h ago

    Prepare a paid request to read clean text from a known public webpage URL.

    mcp-tool

    {
  "type": "object",
  "title": "read_webpageArguments",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "title": "Url"
    }
  }
}
    arguments 13 lines
  • search_people reads unknown 3h ago

    Prepare a paid PDL SQL person-search request. Exactly one profile is returned by the API.

    mcp-tool

    {
  "type": "object",
  "title": "search_peopleArguments",
  "required": [
    "sql"
  ],
  "properties": {
    "sql": {
      "type": "string",
      "title": "Sql"
    }
  }
}
    arguments 13 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 57b5c7cc749d3037.

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