@atlasprimer/mcp-server
https://roleplay.atlasprimer.com
Registry code: 74e719af9c900f6b
Use the `create_roleplay_simulation` tool whenever the user wants to practice, rehearse, or prepare for a high-stakes human conversation (such as enterprise sales objections, difficult performance reviews, executive negotiations, customer de-escalations, or regulatory compliance discussions). Formulate a 1-paragraph scenario prompt defining the learner role, counterpart identity and gender, 3 to 4 behavioral resistance traits, the core conflict, and measurable success criteria, then return the generated clickable simulation URL to the user.
- endpoint
- https://roleplay.atlasprimer.com/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 @atlasprimer/mcp-server live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is @atlasprimer/mcp-server free to use?
- Not measured yet.
- What tools does @atlasprimer/mcp-server have?
- 1 tool: create_roleplay_simulation.
- Is @atlasprimer/mcp-server 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.
90 days 100%· all time 100%
last good check
of 1 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
create_roleplay_simulation unknown never probed
Creates a personalized real-time AI voice roleplay simulation on Atlas Primer from a natural-language scenario description. Returns a direct, clickable simulation URL requiring no API keys or pre-registration.
{ "type": "object", "required": [ "prompt" ], "properties": { "prompt": { "type": "string", "description": "Full 1-paragraph scenario description defining who the user is, who the counterpart is, the core conflict or disagreement, and the stakes." }, "language": { "type": "string", "description": "ISO-639-1 language code such as \"en\", \"is\", \"es\", or \"ja\" (default: \"en\")." }, "user_role": { "type": "string", "description": "Learner role and perspective (e.g., \"Senior Account Executive\")." }, "character_name": { "type": "string", "description": "Counterpart name and title (e.g., \"Elena Rostova, VP of Procurement\")." }, "character_role": { "type": "string", "description": "Counterpart functional role or authority level." }, "character_gender": { "enum": [ "male", "female" ], "type": "string", "description": "Speech synthesis voice gender (\"male\" or \"female\")." }, "failure_criteria": { "type": "string", "description": "Single sentence defining what triggers conversation failure." }, "success_criteria": { "type": "string", "description": "Single unambiguous sentence defining measurable conversation success." }, "challenge_keywords": { "type": "string", "description": "3 to 4 comma-separated behavioral resistance traits (e.g., \"skeptical, defensive, budget-constrained\")." }, "max_duration_minutes": { "type": "number", "description": "Maximum duration in minutes between 3 and 30 (default: 10)." } } }arguments 52 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id74e719af9c900f6b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/74e719af9c900f6b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/74e719af9c900f6b?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.