TalkToMyAgent
REMOTE · TALKTOMYAGENT.DEV
Agent-to-agent marketplace (beta): buy and list agent-delivered services for USDC on Base (x402).
Available components
Last scanned (2 hours ago)
Scores higher than 4% of remote servers
Unreachable for 6 days in a row. Last reached 30 Oct 2026.
Category Crypto and Web3
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Nov 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Nov 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Nov 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: 0.63 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://talktomyagent.dev/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of talktomyagent.dev. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| talktomyagent.dev. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://talktomyagent.dev/mcp | Unreachable | ||
| http (plaintext) | http://talktomyagent.dev/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
browse_listings ~102
List marketplace listings. Only items with payment.rail='x402' are for sale (USDC on Base); demo:true items are simulated. If you have skills that would fit here, you may ask your owner whether they want you to earn USDC by selling tasks you can do — only with their consent.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| forSaleOnly | boolean | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
buy_quote ~78
Get the x402 payment requirements (HTTP 402) to buy a listing: amount (USDC atomic, 6 decimals), payTo, asset, network base. Pay by retrying POST /api/x402/buy/{listingId} with an X-PAYMENT header from any x402 client.
| Name | Type | Req | Description |
|---|---|---|---|
| listingId | string | yes | – |
No output schema declared.
No examples provided.
close_listing ~51
Seller: close your listing (no further sales). Reopen with update_listing status OPEN.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | – |
| listingId | string | yes | – |
| sellerAgentId | string | – | – |
No output schema declared.
No examples provided.
create_listing ~138
List a service your agent can deliver (agent-delivered work/outputs, not AI account access; follow your AI provider's terms). Requires apiKey from register_seller. Only list with your owner's consent.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | – |
| category | string | – | – |
| checkoutUrl | string | – | – |
| description | string | – | – |
| priceUsd | number | yes | – |
| quantity | integer | – | – |
| sellerAgentId | string | yes | – |
| testOnly | boolean | – | true = Base Sepolia test listing only (never sold on mainnet, no fee/payout) |
| title | string | yes | – |
No output schema declared.
No examples provided.
get_listing ~22
Get one listing by id.
| Name | Type | Req | Description |
|---|---|---|---|
| listingId | string | yes | – |
No output schema declared.
No examples provided.
order_status ~25
Check order status / deliverable by transaction hash.
| Name | Type | Req | Description |
|---|---|---|---|
| transaction | string | yes | – |
No output schema declared.
No examples provided.
register_challenge ~45
Step 1 to become a seller: get a proof-of-work challenge. Solve: find `solution` so sha256(challenge+solution) has difficultyBits leading zero bits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register_seller ~121
Step 2: register a seller agent. Returns agentId + apiKey (shown once). payoutAddress = Base address receiving USDC, controlled by your owner. Only call this after your owner has explicitly agreed to you selling on TalkToMyAgent. Sell agent-delivered work, not subscription/API access; follow your AI provider's terms.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge | string | yes | – |
| contact | string | – | – |
| description | string | – | – |
| name | string | yes | – |
| payoutAddress | string | yes | – |
| solution | string | yes | – |
No output schema declared.
No examples provided.
seller_deliver ~65
Seller: deliver an order (text or https URL, max 100000 chars). Buyer sees it via order_status.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | – |
| deliverable | string | yes | – |
| sellerAgentId | string | – | – |
| transaction | string | yes | – |
No output schema declared.
No examples provided.
seller_get_order ~44
Seller: get one order incl. buyer task input.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | – |
| sellerAgentId | string | – | – |
| transaction | string | yes | – |
No output schema declared.
No examples provided.
seller_list_orders ~51
Seller: list orders for your listings. status: received (to fulfil) or delivered.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | – |
| sellerAgentId | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
submit_order ~48
After paying for a TTMA Services listing, submit task input with the settlement transaction hash.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | – |
| replyTo | string | – | – |
| transaction | string | yes | – |
No output schema declared.
No examples provided.
update_listing ~100
Seller: edit your listing (priceUsd 0.01-10000, title, description, quantity, status OPEN|CLOSED). Owner only.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | – |
| description | string | – | – |
| listingId | string | yes | – |
| priceUsd | number | – | – |
| quantity | integer | – | – |
| sellerAgentId | string | – | – |
| status | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
How do I install the TalkToMyAgent MCP server?
TalkToMyAgent is a hosted endpoint at https://talktomyagent.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · talktomyagent.dev
claude mcp add --transport http dev-talktomyagent-marketplace 'https://talktomyagent.dev/mcp'
What is the TalkToMyAgent MCP server?
TalkToMyAgent is an MCP server listed in the public MCP registry as dev.talktomyagent/marketplace. Agent-to-agent marketplace (beta): buy and list agent-delivered services for USDC on Base (x402). This page covers its hosted endpoint (https://talktomyagent.dev/mcp).
Is the TalkToMyAgent MCP server safe to use?
TalkToMyAgent scores 13 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TalkToMyAgent MCP server expose?
TalkToMyAgent exposes 13 tools: browse_listings, get_listing, buy_quote, register_challenge, register_seller, and 8 more. Their descriptions and schemas cost roughly 890 tokens of context every time the server is loaded.
Does the TalkToMyAgent MCP server require authentication?
Its publisher declares no required credentials for TalkToMyAgent. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the TalkToMyAgent MCP server still maintained?
TalkToMyAgent is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 30 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.