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 skills add fxckcode/mcp-cor --skill cor-mcp-setupgit clone --depth 1 https://github.com/fxckcode/mcp-corWrote 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/fxckcode/mcp-cor/cor-mcp-setup)<a href="https://agentmods.dev/skills/fxckcode/mcp-cor/cor-mcp-setup"><img src="https://agentmods.dev/badge/skills/fxckcode/mcp-cor/cor-mcp-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/fxckcode/mcp-cor/cor-mcp-setup"><img src="https://agentmods.dev/badge/skills/fxckcode/mcp-cor/cor-mcp-setup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00047 | $0.00903 |
| Opus 5.5 | $0.00019 | $0.00361 |
| Sonnet 5.5 | $0.00009 | $0.00181 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade C, and why
cor-mcp-setup scanned grade C with 2 findings 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 1mo ago.
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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- `uv` installed (`curl -LsSf https://astral.sh/uv/install.sh | sh`) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `uv` installed (`curl -LsSf https://astral.sh/uv/install.sh | sh`) How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
COR MCP Server
An MCP server that exposes the full Project COR REST API (61 tools) for use from any MCP-compatible agent (Hermes Agent, Claude Desktop, Cursor, Claude Code, etc.).
Prerequisites
- Python 3.11+
uvinstalled (curl -LsSf https://astral.sh/uv/install.sh | sh)- COR credentials (email + password or API key + client secret)
Quick Install
cd /path/to/cor-mcp-server
uv sync
Configuration
Copy .env.example to .env and set ONE authentication mode:
Mode A: Email + Password (personal use)
[email protected]
COR_PASSWORD=your_password
COR_API_URL=https://api.projectcor.com/v1
Mode B: API Key + Client Secret (server-to-server)
COR_API_KEY=your_api_key
COR_CLIENT_SECRET=your_client_secret
COR_API_URL=https://api.projectcor.com/v1
The server auto-detects which mode you configured. Email/password takes priority when both are set.
Running
# stdio (default — for MCP agents)
uv run cor-mcp-server
# SSE/HTTP (for remote access)
uv run cor-mcp-server --transport sse --host 0.0.0.0 --port 8000
Hermes Agent Integration
Add this to your ~/.hermes/config.yaml under mcp_servers:
mcp_servers:
cor:
command: "uv"
args: ["run", "--directory", "/absolute/path/to/cor-mcp-server", "python", "-m", "cor_mcp_server"]
env:
COR_EMAIL: "[email protected]"
COR_PASSWORD: "your_password"
COR_API_URL: "https://api.projectcor.com/v1"
timeout: 180
connect_timeout: 60
Then do /reload-mcp in the Hermes session.
Available Tools (all prefixed with cor_)
| Entity | Count | Key Tools |
|---|---|---|
| Projects | 14 | list, create, update, delete, collaborators, costs, profitability |
| Tasks | 10 | search, create, update, labels, collaborators, my pending |
| Clients | 6 | list, create, update, delete, fees |
| Contracts | 5 | list, create, positions |
| Time Tracking | 5 | log hours, search, change status, accept suggested |
| Team & Users | 8 | profile, users, teams, working time |
| Messaging | 4 | project/task messages |
| Ratecards | 3 | list, get, create |
| Allocations | 3 | by project, save, delete |
| Products | 2 | list, create |
| Labels | 1 | by entity type |
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.
- 1mo ago First seen · 122 lines · 47 tokens per session scan C bdbfbd86ec9c
cor-mcp-setup is a skill published in the GitHub repository fxckcode/mcp-cor (0 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 903 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
reviewing-sla-definitions
Reviewing ServiceNow SLA, OLA and underpinning-contract definitions and how they perform: breach rates per definition, overlapping or duplicated definitions on the same table and target, and definitions that never attach. Use when the user asks about SLA breaches by definition, too many SLAs, duplicate or conflicting…
report-issue
File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.
reviewing-update-sets
Reviewing, analyzing, and comparing ServiceNow update sets before promotion, singly or in batches. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, 'what changed in…
triaging-incidents
Creating, triaging, updating, and analyzing ServiceNow incidents, including trend reports. Assess severity, check affected CIs, find related incidents, and recommend assignments. Use when the user mentions incidents, INC numbers, outages, service disruptions, ticket creation, triage, priority, severity, ITSM…
exploring-tables
Exploring any ServiceNow table: schema, field types, sample records, relationships, and data patterns. Use when the user mentions tables, schemas, fields, data dictionary, sysdictionary, sysdbobject, table structure, 'what fields does X have', or wants to understand a ServiceNow table they haven't worked with before.
assessing-change-impact
Assessing what a ServiceNow change request touched and what followed it: affected CIs, other changes on the same CIs in an overlapping window, and incidents on those CIs after the change, without trusting hidden incident-to-change links. Use this skill whenever the user asks whether a change (a CHG number) caused or…