RFC MCP Server

Created By
mjpitza year ago
An MCP server for fetching RFC related information.
Overview

What is RFC MCP Server?

RFC MCP Server is a server designed for fetching, parsing, and reading RFC (Request for Comments) documents from the ietf.org website, providing tools to interact with these documents programmatically.

How to use RFC MCP Server?

To use the RFC MCP Server, configure your MCP settings file to include the server and utilize the available tools to fetch or search for RFC documents.

Key features of RFC MCP Server?

  • Fetch RFC documents by number
  • Search for RFCs by keyword
  • Extract specific sections from RFC documents
  • Support for both HTML and TXT formats
  • Caching for improved performance

Use cases of RFC MCP Server?

  1. Developers can programmatically access RFC documents for integration into applications.
  2. Researchers can search and retrieve specific RFCs related to their work.
  3. Educators can use the server to fetch RFCs for teaching purposes.

FAQ from RFC MCP Server?

  • Can I fetch any RFC document?

Yes! You can fetch any RFC document by its number.

  • How do I search for RFCs?

You can search for RFCs using keywords through the search functionality.

  • What formats does the server support?

The server supports both HTML and TXT formats for RFC documents.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mjpitz
Star
1
Language
TypeScript
License
Apache-2.0 license
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago