Cdgcsearchmetadata

io.github.poojaBjAcharyaPublished by GitHub account poojaBjAcharyav1.0.0Updated Oct 24, 2026

Provides metadata information to AI agents through the search API.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP server that gives AI agents metadata information through a search API, reached over streamable HTTP with OAuth.

What you can do
Exposes a search API that returns metadata information to AI agents. The manifest lists no individual tools, so the exact operations are not documented here. Access is over a remote streamable HTTP endpoint rather than a local package.
When to use it
Consider it when an assistant needs metadata lookups from this provider's search API and you already have authorized access to the endpoint.
Requirements
A remote streamable HTTP endpoint at the provider's QA host, with OAuth authentication required. A bearer token must be supplied in the Authorization header. No local runtime or environment variables are declared.
Before you install
The endpoint is on a QA host, so treat its data as non-production. You must supply a bearer token in the Authorization header; keep it secret and note that queries and the token are sent to a third-party server.

Installation

In SourceWeft

  1. Open Cdgcsearchmetadata in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.poojaBjAcharya%2Fcdgcsearchmetadata/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "cdgcsearchmetadata": {
      "type": "http",
      "url": "https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.