Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.poojaBjAcharya/cdgcsearchmetadata

REMOTE · QA-POD1-A2E-MCP.REL.INFAQA.COM · SCANNED AUG 3

Provides metadata information to AI agents through the search API.

Available components

remote · qa-pod1-a2e-mcp.rel.infaqa.com 33
+12 this week 33 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security83
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → 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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · qa-pod1-a2e-mcp.rel.infaqa.com

# add to Claude Code
claude mcp add --transport http poojabjacharya-cdgcsearchmetadata https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata
# ~/.codex/config.toml
[mcp_servers.poojabjacharya-cdgcsearchmetadata]
url = "https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "poojabjacharya-cdgcsearchmetadata": {
      "type": "remote",
      "url": "https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add poojabjacharya-cdgcsearchmetadata --url https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  poojabjacharya-cdgcsearchmetadata:
    url: "https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata"
// mcp.json
{
  "mcpServers": {
    "poojabjacharya-cdgcsearchmetadata": {
      "type": "http",
      "url": "https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 31 Jul 26 +12
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 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
  • 27 Jul 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
  • 26 Jul 26 21

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Probed https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=qa-a2e.rel.infaqa.com,O=Informatica LLC,L=Redwood City,ST=California,C=US CN=HydrantID Server CA O1,OU=HydrantID Trusted Certificate Service,O=IdenTrust,C=US 9 Jun 2026 25 Dec 2026 RSA 2048 SHA256-RSA 40019eab9e52ccb59bd32c3ce29eb3d6
SANs: qa-a2e.rel.infaqa.com, hdm.qa-ma.rel.infaqa.com, mcp.qa-ma.rel.infaqa.com, qa-a2e-mcp.rel.infaqa.com, qa-pod1-a2e.rel.infaqa.com, qa-pod2-a2e.rel.infaqa.com, qa-pod1-a2e-mcp.rel.infaqa.com, qa-pod2-a2e-mcp.rel.infaqa.com
CN=HydrantID Server CA O1,OU=HydrantID Trusted Certificate Service,O=IdenTrust,C=US (CA) CN=IdenTrust Commercial Root CA 1,O=IdenTrust,C=US 12 Dec 2019 12 Dec 2029 RSA 2048 SHA256-RSA 40016efb0a205cfaebe18f71d73abb78
CN=IdenTrust Commercial Root CA 1,O=IdenTrust,C=US (CA) CN=IdenTrust Commercial Root CA 1,O=IdenTrust,C=US 16 Jan 2014 16 Jan 2034 RSA 4096 SHA256-RSA a0142800000014523c844b500000002
DNSSEC insecure

Validation of qa-pod1-a2e-mcp.rel.infaqa.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
infaqa.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On connection
HTTP status 401

Protected resource metadata

Retrieved No
Problem no_resource_metadata
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata Auth required 401
http (plaintext) http://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata HTTPS enforced
MCP tools

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.

No tool schema has been captured from this endpoint yet.