Is the Gsc Em Aio Agents MCP server down?

mcp-registry/io.github.gsc-em/aio-agents-mcp · v1.0.3

Also listed as glama/greencore-solutions/mcp-cpg-human-in-the-loop-hitl-, mcp-registry/io.github.greencore-solutions/cpg-human-in-the-loop

unknown
Last checked 2026-10-17 02:54 UTC

As of 2026-10-17 02:54 UTC, the Gsc Em Aio Agents MCP server is unknown with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.6%
checks observed
2,713
outages (90d)
3
tools
9

CPG Human In The Loop — HITL transaction MCP. Machines lodge; humans decide. By GreenCore Solutions.

Point your MCP client at this streamable-http endpoint: https://mcp.cpghumanintheloop.ai/mcp

Agent-readiness: C (71/100)

C (71/100): 1 error(s), 3 warning(s) across 4 tool(s); ~1,028 tokens of tool definitions.
Scores higher than 7% of 15,327 MCP servers Glimind has audited.
Its tool list costs an agent ~1,028 tokens per session — more than 25% of servers.
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability0
Stability100

What to fix (5)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST.

4 of 4 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.

Tools: check_rfq_status, escalate, request_terms, submit_rfq

1 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.

Tools: submit_rfq

Handshake + tools/list takes ~1,974 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.

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.gsc-em%2Faio-agents-mcp/fixes

check_rfq_status 1 change
{
  "name": "check_rfq_status",
  "description": "Poll a ticket previously lodged on this MCP (RFQ, terms request, or escalation). Returns current status and, once a human has answered, the answer.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "ticket_id"
    ],
    "properties": {
      "ticket_id": {
        "type": "string",
        "pattern": "^HITL-\\d{8}-[A-F0-9]{6}$",
        "description": "Ticket ID returned at submission, e.g. HITL-20260719-A1B2C3"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Check ticket status"
}
submit_rfq 1 change
{
  "name": "submit_rfq",
  "description": "Lodge a request-for-quotation with GreenCore Solutions Corp. A human reviews and answers every ticket — no order is decided by this tool. Returns a ticket ID for polling via check_rfq_status. Optionally reference a GTIN resolved on mcp.cpgknowledgegraph.ai and an SM-ECO-10060 market code.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "subject",
      "details",
      "requester_name",
      "requester_contact"
    ],
    "properties": {
      "gtin": {
        "type": "string",
        "maxLength": 14,
        "description": "Optional GTIN reference (as resolved on the CPG Knowledge Graph)"
      },
      "market": {
        "type": "string",
        "maxLength": 8,
        "description": "Optional SM-ECO-10060 member code, e.g. FR, AU, MX"
      },
      "details": {
        "type": "string",
        "maxLength": 8000,
        "minLength": 3,
        "description": "Full request: product, volumes, timing, destination"
      },
      "subject": {
        "type": "string",
        "maxLength": 300,
        "minLength": 3,
        "description": "One-line summary of the RFQ"
      },
      "quantity": {
        "type": "string",
        "maxLength": 200,
        "description": "Optional quantity / volume expression"
      },
      "requester_name": {
        "type": "string",
        "maxLength": 200,
        "description": "Requesting organization or agent operator"
      },
      "requester_contact": {
        "type": "string",
        "maxLength": 300,
        "description": "Reply channel: email or URL a human can answer to"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Submit RFQ"
}

Get alerted

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.gsc-em/aio-agents-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.gsc-em/aio-agents-mcp"}) over MCP.

Passed

Largest tool definitions

Static 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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.gsc-em%2Faio-agents-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.gsc-em%2Faio-agents-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.gsc-em%2Faio-agents-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.gsc-em%2Faio-agents-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.gsc-em%2Faio-agents-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.gsc-em%2Faio-agents-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:40e1ede5c32398d5…, first seen 2026-10-17, included at leaf 4712 of 18,994. Version history · verify what your client received.

Tools (9)

Compare: most reliable knowledge servers · most reliable data servers · most reliable communication servers · most reliable analytics servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Gsc Em Aio Agents MCP server down right now?

As of 2026-10-17 02:54 UTC, the Gsc Em Aio Agents MCP server is unknown with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Gsc Em Aio Agents MCP server provide?

Gsc Em Aio Agents MCP server advertises 9 tools, including check_rfq_status, count_attribution_coverage, escalate, find_banners, get_agentic_readiness.

How do I install Gsc Em Aio Agents MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.cpghumanintheloop.ai/mcp

Is the Gsc Em Aio Agents MCP server safe to connect to an AI agent?

Glimind scanned all 4 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.

Operator of Gsc Em Aio Agents MCP server?

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.