GetMyData

MCP server · getmydata.io · found in a public list · checked since 2026-10-24

Live, handshake completed · latest check 2026-10-25 00:16 UTC

As JSON

https://getmydata.io/mcp MCP endpoint (Streamable HTTP)

The name is the registry's label, not ours. Not reviewed by a person.

Our checks

An unpaid request daily, from eastern North America

Last 2 checks, oldest to newest; room for 28 more

2 passed, 0 failed, 28 not run.

Passed, 30 daysshort history2 of 2 run

Checks missed0in 30 days

Response, latest551 mswhole handshake

Scheduledailyset by usage; rule below

Checked since2026-10-241 day

Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Response times

Window	Checks	Median	90th	95th	99th	Fastest	Slowest
24 hours	1	—	—	—	—	—	—
7 dayssince 2026-10-24	2	—	—	—	—	—	—
30 dayssince 2026-10-24	2	—	—	—	—	—	—

Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of 2026-10-25 00:20 UTC. Definitions and method.

Details

Tools listed by the server

cancel_collectioncancel_requestconfirm_quoteconfirm_scopecreate_orderfetch_deliveryget_orderget_payment_statusget_quoteget_requestrefresh_sessionrevise_requisitionstart_email_verificationstart_ordersubmit_requisitionverify_email

Tools: 16
This list since: 2026-10-24
First listed to us: 2026-10-24
List changes, 90 days: 0

Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions

Access

Our latest check: Nothing asked2026-10-25 00:16 UTC
Stated: not stated
Payment model: not known
Currency: not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Interface it declares

Protocol: MCP 2025-03-26
Capabilities: tools
Transports: streamable-http

As its initialize reply stated it at our check on 2026-10-25 00:16 UTC (mcp-handshake/2): a claim, not tested. Definitions

Calls it declares

refresh_session idempotency_key*
submit_requisition human_email* sources* fields* dedup_keys row_target* row_commitment* filters* geo* deadline* language* description* search_keywords coupon_code channel_id prior_request_capability
get_request request_id* request_capability*
revise_requisition request_id* request_capability* human_email sources* fields* dedup_keys row_target* row_commitment* filters* geo* deadline* language* description* search_keywords coupon_code
confirm_scope request_id* request_capability* expected_revision* sample_id idempotency_key*
confirm_quote request_id* request_capability* quote_id* expected_revision* idempotency_key*
start_email_verification request_id* request_capability* human_email idempotency_key*
verify_email request_id* request_capability* otp* idempotency_key*
start_order request_id* request_capability* quote_id* expected_revision* human_email idempotency_key*
create_order request_id* request_capability* quote_id* expected_revision* otp coupon_codes idempotency_key*
cancel_request request_id* request_capability* expected_revision* idempotency_key*
get_quote request_id* request_capability*

From the tool list it returned to our check (request-shape/1). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.

Listing

In the capability tree: Other (not placed in a branch yet) (primary). Placed by keyword rules (placement-rules/3, tree/3) on 2026-10-24. Wrong place? Tell us.

In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✗ what it does is unclear to our placement; ✓ its latest check passed.

Recent probes

When	Result	Time to headers
2026-10-25 00:16 UTC cloudflare:EWR	Live, handshake completed HTTP 200	551 ms
2026-10-24 00:10 UTC cloudflare:MIA	Live, handshake completed HTTP 200	1518 ms

What these figures do not show

A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
Limited evidence: monitored for 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_5a6cdb698cd7e155