Skip to content
Back to skills

137 Mcp Eb4ab38d

ASecurity

MCP is JSON-RPC 2.0 based protocol for AI-tool integration.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
toolstypescriptnodesecurity

Works with

  • cli
  • mcp

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 137-mcp_eb4ab38d --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 137 Mcp Eb4ab38d?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 137 Mcp Eb4ab38d
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-137-mcp-eb4ab38d/badge)](https://www.skillsdirectory.com/skills/tools-only-137-mcp-eb4ab38d)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
# Model Context Protocol (MCP) Reference

## Protocol Overview

MCP is JSON-RPC 2.0 based protocol for AI-tool integration.

**Version**: 2025-03-26
**Foundation**: JSON-RPC 2.0
**Architecture**: Client-Host-Server

## Connection Lifecycle

1. **Initialize**: Client sends `initialize` request with capabilities
2. **Response**: Server responds with its capabilities
3. **Handshake**: Client sends `notifications/initialized`
4. **Active**: Bidirectional messaging
5. **Shutdown**: Close connections, cleanup

## Core Capabilities

### Tools (Executable Functions)

Tools are functions that servers expose for execution.

**List Tools**:
```json
{"method": "tools/list"}
```

**Call Tool**:
```json
{
  "method": "tools/call",
  "params": {
    "name": "tool_name",
    "arguments": {}
  }
}
```

### Prompts (Interaction Templates)

Prompts are reusable templates for LLM interactions.

**List Prompts**:
```json
{"method": "prompts/list"}
```

**Get Prompt**:
```json
{
  "method": "prompts/get",
  "params": {
    "name": "prompt_name",
    "arguments": {}
  }
}
```

### Resources (Data Sources)

Resources expose read-only data to clients.

**List Resources**:
```json
{"method": "resources/list"}
```

**Read Resource**:
```json
{
  "method": "resources/read",
  "params": {"uri": "resource://path"}
}
```

## Transport Types

### stdio (Local)

Server runs as subprocess. Messages via stdin/stdout.

```typescript
const transport = new StdioClientTransport({
  command: 'node',
  args: ['server.js']
});
```

### HTTP+SSE (Remote)

POST for requests, GET for server events.

```typescript
const transport = new StreamableHTTPClientTransport({
  url: 'http://localhost:3000/mcp'
});
```

## Error Codes

- **-32700**: Parse error
- **-32600**: Invalid request
- **-32601**: Method not found
- **-32602**: Invalid params
- **-32603**: Internal error
- **-32002**: Resource not found (MCP-specific)

## Best Practices

1. **Progressive Disclosure**: Load tool definitions on-demand
2. **Context Efficiency**: Filter data before returning
3. **Security**: Validate inputs, sanitize outputs
4. **Resource Management**: Cleanup connections properly
5. **Error Handling**: Handle all error cases gracefully

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…