mcp-registry/io.github.mickeyappol-create/apex · vmcp-server-v1
As of 2026-10-20 13:18 UTC, the Mickeyappol Create Apex MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 28 outages in 90 days, with a median recovery of 5 minutes.
Run verified read-only code tools: quant diagnostics + agent-ops preflight, no source exposure.
Claude Code
claude mcp add --transport http mickeyappol-create-apex-mcp-server https://smartapex.uk/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"mickeyappol-create-apex-mcp-server": {
"type": "http",
"url": "https://smartapex.uk/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
92 parameter(s) across 23 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
19 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Handshake + tools/list takes ~2,563 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
1 of 24 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 23 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.mickeyappol-create%2Fapex/fixes
{
"name": "apex_run_agent_release_readiness_gate",
"description": "Aggregate caller-supplied boolean release-check declarations into PASS/WATCH/BLOCK. Does not run CI, inspect files, verify the declarations, or authorize publication.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"checks"
],
"properties": {
"build": {
"description": "Deprecated. Ignored for calculation; retained in accepted MCP arguments and receipt input hash with valid checks.",
"type": "string"
},
"tests": {
"description": "Deprecated. Ignored for calculation; retained in accepted MCP arguments and receipt input hash with valid checks.",
"type": "string"
},
"checks": {
"type": "object",
"properties": {
"i18n": {
"type": "boolean"
},
"build": {
"type": "boolean"
},
"tests": {
"type": "boolean"
},
"rollback": {
"type": "boolean"
},
"typecheck": {
"type": "boolean"
},
"monitoring": {
"type": "boolean"
},
"secret_scan": {
"type": "boolean"
},
"api_contract": {
"type": "boolean"
},
"db_migration": {
"type": "boolean"
},
"no_raw_source": {
"type": "boolean"
},
"license_review": {
"type": "boolean"
},
"signed_wrappers": {
"type": "boolean"
}
},
"description": "Required partial object of caller-declared booleans. Omitted checks count false; no evidence objects.",
"additionalProperties": false
},
"rollback": {
"description": "Deprecated. Ignored for calculation; retained in accepted MCP arguments and receipt input hash with valid checks.",
"type": "string"
},
"typecheck": {
"description": "Deprecated. Ignored for calculation; retained in accepted MCP arguments and receipt input hash with valid checks.",
"type": "string"
},
"monitoring": {
"description": "Deprecated. Ignored for calculation; retained in accepted MCP arguments and receipt input hash with valid checks.",
"type": "string"
},
"secret_scan": {
"description": "Deprecated. Ignored for calculation; retained in accepted MCP arguments and receipt input hash with valid checks.",
"type": "string"
},
"no_raw_source": {
"description": "Deprecated. Ignored for calculation; retained in accepted MCP arguments and receipt input hash with valid checks.",
"type": "string"
},
"license_review": {
"description": "Deprecated. Ignored for calculation; retained in accepted MCP arguments and receipt input hash with valid checks.",
"type": "string"
},
"signed_wrappers": {
"description": "Deprecated. Ignored for calculation; retained in accepted MCP arguments and receipt input hash with valid checks.",
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
},
"title": "Run Agent Release Readiness Gate"
}{
"name": "apex_submit_review",
"description": "Submit a safe usage review tied to an existing Apex verification receipt. Permissionless bounded receipts need only the receipt. Verified receipts require signed Agent Passport request headers with review intent and asset:review capability; agent_id alone is not authentication. Sign the full JSON-RPC body and API-visible POST /mcp path, including through Target5 /api/mcp. Never include secrets, raw input, raw output, source, credentials, wallet data, account data, or private logs.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"card_id",
"schema",
"receipt_id",
"tool_id",
"usefulness_score",
"worked",
"use_case",
"public_summary"
],
"properties": {
"schema": {
"type": "string",
"const": "apex-usage-review/1"
},
"worked": {
"type": "boolean"
},
"card_id": {
"type": "string",
"maxLength": 120,
"minLength": 1
},
"tool_id": {
"type": "string",
"maxLength": 120,
"minLength": 1
},
"agent_id": {
"type": "string",
"maxLength": 120,
"minLength": 1
},
"use_case": {
"type": "string",
"maxLength": 220,
"minLength": 4
},
"receipt_id": {
"type": "string",
"maxLength": 160,
"minLength": 16
},
"agent_client": {
"type": "string",
"maxLength": 120
},
"problem_found": {
"type": "string",
"maxLength": 800
},
"public_summary": {
"type": "string",
"maxLength": 1000,
"minLength": 20
},
"usefulness_score": {
"type": "integer",
"maximum": 5,
"minimum": 1
},
"requested_improvement": {
"type": "string",
"maxLength": 800
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Submit Target5 Usage Review"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.mickeyappol-create/apex"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.mickeyappol-create/apex"}) over MCP.
apex_run_agent_release_readiness_gate ~627 tokensapex_submit_review ~400 tokensapex_run_strategy_gatekeeper ~309 tokensapex_run_alphalens_factor_research ~250 tokensapex_query_dataset ~247 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.mickeyappol-create%2Fapex?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.mickeyappol-create%2Fapex?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mickeyappol-create%2Fapex.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mickeyappol-create%2Fapex.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.mickeyappol-create%2Fapex?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:df5695e2e8bd4759…, first seen 2026-10-17, included at leaf 887 of 33,103. Version history · verify what your client received.
Compare: most reliable files servers · most reliable search servers · most reliable data servers · most reliable code servers · most reliable devops servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 13:18 UTC, the Mickeyappol Create Apex MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 28 outages in 90 days, with a median recovery of 5 minutes.
Mickeyappol Create Apex MCP server advertises 24 tools, including apex_get_card, apex_query_cards, apex_query_dataset, apex_run_agent_api_contract_diff, apex_run_agent_data_profile.
Point your MCP client at this streamable-http endpoint: https://smartapex.uk/api/mcp
Glimind scanned all 24 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.