io.github.jyswee/ainpc-cli
REMOTE · MCP.AINPCENGINE.COM · 3 COMPONENTS
AI NPCs with persistent memory for game studios. NPC CRUD, dialogue, voice. Stdio or remote SSE.
Available components
Last scanned (23 hours ago)
Scores higher than 8% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Entertainment and Games
Recent critical change
Authorization (13 Oct 2026). See the changelog before you install this server.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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 check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared sse, but the endpoint returned HTTP 429. 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.
- 16 Oct 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 13 Oct 26 +50
- Authorization: unverified → fail ▼ critical
- Stability: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 29 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Authorization: unverified → fail ▼ critical
- Stability: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 23 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 20 Sept 26 0
- Server version: 1.0.0 → 1.1.0 functional
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 4 Nov 2026 · Probed https://mcp.ainpcengine.com/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ainpcengine.com | CN=YR1,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | RSA 4096 | SHA256-RSA | 5595ed73f91971690ae26d2174c2743c268 |
| SANs: *.ainpcengine.com, ainpcengine.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.ainpcengine.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ainpcengine.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 429 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcp.ainpcengine.com/sse | HTTP error | 429 | |
| http (plaintext) | http://mcp.ainpcengine.com/sse | HTTPS enforced | 301 | https://mcp.ainpcengine.com/sse |
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 →
ainpc_get_started ~35
Explains what AINPCEngine is and how to activate this MCP server (no API key on this session yet).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ainpc_signup ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Human email. Used to log in and activate the trial. | |
| name | string | yes | Studio display name, e.g. "My Game Studio" |
| password | string | yes | Account password (min 8 characters) |
| plan | string | – | Plan (default: indie, $29/mo after trial) |
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Full npk_ API key — returned exactly once |
| keyPrefix | string | yes | Key prefix |
| next | string | yes | Human-readable next-step instructions |
| paymentUrl | string | yes | URL where a card must be added to start the trial (API is 402-gated until then) |
| studio | object | yes | Created studio |
| trial | object | yes | Trial terms |
No examples provided.
How do I install the io.github.jyswee/ainpc-cli MCP server?
io.github.jyswee/ainpc-cli is a hosted endpoint at https://mcp.ainpcengine.com/sse, 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 · mcp.ainpcengine.com
claude mcp add --transport http jyswee-ainpc-cli 'https://mcp.ainpcengine.com/sse'
What is the io.github.jyswee/ainpc-cli MCP server?
io.github.jyswee/ainpc-cli is an MCP server listed in the public MCP registry as io.github.jyswee/ainpc-cli. AI NPCs with persistent memory for game studios. NPC CRUD, dialogue, voice. Stdio or remote SSE. This page covers its hosted endpoint (https://mcp.ainpcengine.com/sse).
Is the io.github.jyswee/ainpc-cli MCP server safe to use?
io.github.jyswee/ainpc-cli scores 23 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 io.github.jyswee/ainpc-cli MCP server expose?
io.github.jyswee/ainpc-cli exposes 2 tools: ainpc_get_started, ainpc_signup. Their descriptions and schemas cost roughly 196 tokens of context every time the server is loaded.
Does the io.github.jyswee/ainpc-cli MCP server require authentication?
Its publisher declares no required credentials for io.github.jyswee/ainpc-cli. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.jyswee/ainpc-cli MCP server still maintained?
io.github.jyswee/ainpc-cli is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.