Cdgcsearchmetadata MCP Server
io.github.poojaBjAcharya/cdgcsearchmetadata
answering
Cdgcsearchmetadata is answering right now. Last checked 7 min ago.
Provides metadata information to AI agents through the search API.
The linked repository no longer exists on GitHub — it was deleted or made private.
Uptime history
39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
635 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.
run in your terminal
claude mcp add cdgcsearchmetadata --transport http https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"cdgcsearchmetadata": {
"url": "https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata"
}
}
}~/.codex/config.toml
[mcp_servers.cdgcsearchmetadata]
url = "https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata".cursor/mcp.json
{
"mcpServers": {
"cdgcsearchmetadata": {
"url": "https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"cdgcsearchmetadata": {
"url": "https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata"
}
}
}This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata | streamable-http | needs key | 658 ms | 7 min ago |
Cdgcsearchmetadata — questions
Answers built from our own checks of this server.
Why is there no tool list for Cdgcsearchmetadata?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Cdgcsearchmetadata working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 635 ms. The bar chart above shows every period we have measured.
Is Cdgcsearchmetadata still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Cdgcsearchmetadata?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Cdgcsearchmetadata need an API key?
Yes. Every time we knock, Cdgcsearchmetadata answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Cdgcsearchmetadata?
It answers our handshake in 635 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.