_ registry / mcp http-sse · checked 12m ago

ainpcengine

https://mcp.ainpcengine.com

Registry code: fc2f6eb3b7509a79

api record

AI NPCs with persistent memory for game studios. NPC CRUD, dialogue, voice. Stdio or remote SSE.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.ainpcengine.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 ainpcengine live?
Yes — it answered the hub's last check (checked 12m ago). It answered 99% of checks over the last 30 days.
Is ainpcengine free to use?
Yes — the hub reached it with no key and no payment.
What tools does ainpcengine have?
2 tools: ainpc_signup, ainpc_get_started.
Is ainpcengine 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 99.1%· all time 99.1%

latency
211ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 329 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
games & entertainment games
used for
  • learn how to set up game npcs with memory
  • create a studio account
takes → gives
text → text
tools
1 reads1 changes data
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

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

  • ainpc_get_started reads open 16h ago

    Explains what AINPCEngine is and how to activate this MCP server (no API key on this session yet).

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • ainpc_signup changes data unknown never probed

    Create a new AINPCEngine studio account. Requires the human's email and a password (min 8 chars): they log in at ainpcengine.com and add a card to start the 7-day free trial ($0 today). Returns an npk_ API key (shown once) and unlocks all AINPCEngine tools in this session immediately. Ask the human for their email before calling.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "email",
    "password"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Studio display name, e.g. \"My Game Studio\""
    },
    "plan": {
      "enum": [
        "indie",
        "pro",
        "enterprise"
      ],
      "type": "string",
      "description": "Plan (default: indie, $29/mo after trial)"
    },
    "email": {
      "type": "string",
      "description": "Human email. Used to log in and activate the trial."
    },
    "password": {
      "type": "string",
      "description": "Account password (min 8 characters)"
    }
  }
}
    arguments 31 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 fc2f6eb3b7509a79.

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

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.