yahoo-finance-mcp@0.1.0
VERIFIED· install onlyPublisher claims: "Enables MCP clients such as Claude, ChatGPT, and Notion to retrieve Yahoo Finance quotes, price history, fundamentals, analyst and holder data, options, funds, screeners, market summaries, calendars, and live ticks through 24 tools. It supports remote Streamable HTTP access with OAuth 2.1, Basic auth, and client credentials." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
OAUTH_CLIENT_IDOAUTH_CLIENT_SECRETOAUTH_REDIRECT_URISOAUTH_SIGNING_KEYor--set-secrets/--allow-unauthenticatedConfiguration, not credentials: PUBLIC_BASE_URL- Where it talks to
- no vendor host named in the codeAlso claude.ai, claude.com, notion.com, chatgpt.com, run.app, yahoo.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names claude.ai, claude.com, notion.com, chatgpt.com, run.app, yahoo.com as well as its own vendor. The guard injects OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET, OAUTH_REDIRECT_URIS, OAUTH_SIGNING_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-11 and scored it 84/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
cp .env.example .env # then set OAUTH_CLIENT_SECRET (openssl rand -hex 32)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.set -a; . ./.env; set +aFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…project IDs or numbers, real service URLs). Real values live only in the local `.env`, which is gitignored along with `.dockerignore`/`.gcloudignore` exclusions. - …Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Register the OAuth endpoints as MCPServer custom routes. The config is created at startup, so it is passed as a getter."""Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.out = subprocess.run([sys.executable, "auth.py", "issue-token", "--days", "1", "--base-url", live_server],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Add a custom connector (Settings → Connectors, developer mode) with:Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Add a custom connector (Settings → Connectors, developer mode) with:Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.