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 rules/jhgaylor/node-candidate-mcp-server/typescript-mcpgit clone --depth 1 https://github.com/jhgaylor/node-candidate-mcp-serverWhat 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.00000 | $0.01379 |
| Opus 5 | $0.00000 | $0.00690 |
| Sonnet 5 | $0.00000 | $0.00276 |
| Haiku 4.5 | $0.00000 | $0.00138 |
Grade A, and why
typescript-mcp scanned grade A with 0 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 2d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP TypeScript SDK
MCP TypeScript SDK implements the full Model Context Protocol specification, allowing you to build MCP servers and clients using TypeScript.
Installation
npm install @modelcontextprotocol/sdk --save
# or
yarn add @modelcontextprotocol/sdk
Quickstart: Create an MCP Server
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({ name: "DemoServer", version: "1.0.0" });
// Define a simple addition tool
type AddParams = { a: number; b: number };
server.tool(
"add",
{ a: z.number(), b: z.number() },
async ({ a, b }: AddParams) => ({ content: [{ type: "text", text: `${a + b}` }] })
);
// Start listening on stdin/stdout transport
await server.connect(new StdioServerTransport());
Core Concepts
- McpServer: entry point for protocol compliance, message routing, and lifecycle management.
- Resources: read-only data endpoints via
server.resource(name, template, handler)andResourceTemplate. - Tools: action endpoints via
server.tool(name, schema, executor). - Prompts: reusable message templates via
server.prompt(name, schema, builder). - Transports: connect servers/clients over stdio, HTTP, SSE, or Streamable HTTP (
StdioServerTransport,StreamableHttpServerTransport, etc.).
Preferred Transport: Streamable HTTP
Streamable HTTP is the recommended transport for production environments, offering full-duplex streaming, session management, and backward compatibility over older SSE-based transports.
Streamable HTTP Server Example
import express from "express";
import { randomUUID } from "crypto";
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StreamableHTTPServerTransport } from "@modelcontextprotocol/sdk/server/streamableHttp.js";
import { isInitializeRequest } from "@modelcontextprotocol/sdk/types.js";
const app = express();
app.use(express.json());
const server = new McpServer({ name: "StreamableExample", version: "1.0.0" });
const transports: Record<string, StreamableHTTPServerTransport> = {};
app.post('/mcp', async (req, res) => {
const sid = req.headers['mcp-session-id'] as string | undefined;
let transport: StreamableHTTPServerTransport;
if (sid && transports[sid]) {
transport = transports[sid];
} else if (!sid && isInitializeRequest(req.body)) {
transport = new StreamableHTTPServerTransport({
sessionIdGenerator: () => randomUUID(),
onsessioninitialized: (sessionId) => (transports[sessionId] = transport)
});
transport.onclose = () => delete transports[transport.sessionId!];
} else {
res.status(400).send("Invalid request");
return;
}
await server.connect(transport);
transport.handleRequest(req, res);
});
const PORT = process.env.PORT ?? 3000;
app.listen(PORT, () => console.log(`MCP Streamable HTTP server listening on ${PORT}`));
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.
- 2d ago First seen · 172 lines · 1,379 tokens per session scan A 21d73a58daff
typescript-mcp is a cursor rule published in the GitHub repository jhgaylor/node-candidate-mcp-server (81 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,379 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
cursorrules
You can control Streamfog AR lenses, face filters, and Vtuber avatars on the live OBS stream via the Streamer.bot bridge (5 MCP tools: streamfogstatus, streamfogsetlens, streamfogcleareffects, streamfogtoggleavatar, streamfoglistlenses).
p
Go项目开发规则 - 遵循Go最佳实践,不使用checkout和reset命令.
typescript-mcp
Cursor rule "typescript-mcp" from jhgaylor/ai-jakegaylor-com, covering installation, or, quickstart: create an mcp server, core concepts and preferred transport: streamable http.
mcp
MCP is a standard protocol to exchange contextual data between clients, servers, and LLMs. This rule provides an at-a-glance reference for key concepts, spec versions, tooling, and best practices.
webdesigner
Cursor rule "webdesigner" from jhgaylor/ai-jakegaylor-com, covering web designer expert, expertise, information architecture, tailwindcss techniques and express.js static site guidelines.
cursorrules
The Outline API is not purely RESTful. All endpoints use POST and never GET, PUT, or any other HTTP method.