Remote MCP · Endpoint

Tamer Prompt Marketplace MCP server

No. Tamer Prompt Marketplace answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agents.tamer-ai.ir/mcp

The last check completed an MCP handshake.

Registry name
io.github.parvizrahayan/tamer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
161 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Prompt marketplace for AI agents: browse and buy prompts with x402 (USDC on Base).
Listing
From the official MCP registry (active).
Recent checks of Tamer Prompt Marketplace
CheckedResultHandshake
1 hour agoHandshake completed161 ms
6 hours agoHandshake completed296 ms
2 days agoHandshake completed229 ms
4 days agoHandshake completed169 ms
7 days agoHandshake completed177 ms
9 days agoHandshake completed165 ms
11 days agoHandshake completed46 ms
13 days agoHandshake completed155 ms
15 days agoHandshake completed196 ms
17 days agoHandshake completed178 ms
19 days agoHandshake completed42 ms
21 days agoHandshake completed159 ms
23 days agoHandshake completed390 ms
24 days agoHandshake completed360 ms
25 days agoHandshake completed125 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Tamer Prompt Marketplace and makes no claim about it beyond what these checks measured.