Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/yourdaylight/stock_datasource/mcp-api-key-authnpx skills add Yourdaylight/stock_datasource --skill mcp-api-key-authgit clone --depth 1 https://github.com/Yourdaylight/stock_datasourceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/yourdaylight/stock_datasource/mcp-api-key-auth)<a href="https://agentmods.dev/skills/yourdaylight/stock_datasource/mcp-api-key-auth"><img src="https://agentmods.dev/badge/skills/yourdaylight/stock_datasource/mcp-api-key-auth.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00057 | $0.01299 |
| Opus 5 | $0.00028 | $0.00649 |
| Sonnet 5 | $0.00011 | $0.00260 |
| Haiku 4.5 | $0.00006 | $0.00130 |
Grade A, and why
mcp-api-key-auth scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
JWT=$(curl -s -X POST http://<host>:8000/api/auth/login \ How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Enable external MCP clients (Claude Code, Cursor, PicoClaw, DeepSeek Harness) to authenticate with the stock data service using independent API keys, and track per-tool usage (table name, record count) for monitoring.
When to Use
- User wants to create or manage MCP API keys
- User wants to configure an external MCP client to connect to this service
- User wants to view MCP tool usage statistics (which tools called, which tables queried, how many records)
- User needs to troubleshoot MCP authentication errors (401, invalid key, expired key)
Architecture
- API Key management is on the HTTP server (port 8000), protected by JWT login
- MCP protocol is on the MCP server (port 8001), protected by API key in request headers
- Usage tracking records are stored in ClickHouse
mcp_tool_usage_logtable
Workflow
1) Create an API Key
First login to get a JWT token, then create an API key:
# Login
JWT=$(curl -s -X POST http://<host>:8000/api/auth/login \
-H "Content-Type: application/json" \
-d '{"email":"[email protected]","password":"yourpassword"}' \
| python3 -c "import sys,json; print(json.load(sys.stdin)['access_token'])")
# Create API key
curl -s -X POST http://<host>:8000/api/mcp-keys/create \
-H "Authorization: Bearer $JWT" \
-H "Content-Type: application/json" \
-d '{"key_name": "my-cursor-key", "expires_days": 90}'
The response contains the full API key (e.g., sk-a1b2c3d4...). Save it immediately — it is only shown once.
2) Configure MCP Client
Claude Code / Claude Desktop
Add to your MCP configuration (claude_desktop_config.json or project .mcp.json):
{
"mcpServers": {
"stock-data": {
"url": "http://<host>:8001/messages",
"transport": "streamable-http",
"headers": {
"Authorization": "Bearer sk-your-api-key-here"
}
}
}
}
Cursor
In Cursor settings, add an MCP server with:
- URL:
http://<host>:8001/messages - Header:
Authorization: Bearer sk-your-api-key-here
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today Changed · +4 lines bb28b0e25bb6
- 5d ago First seen · 134 lines · 57 tokens per session scan A 8c2dcc2f7f62
mcp-api-key-auth is a skill published in the GitHub repository Yourdaylight/stock_datasource (183 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 1,299 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…