Developer · Remote MCP server
Feode MCP
FEODE: AI-accessible precision machining & testing; offshore P&A, subsea wellhead, drill-pipe.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.feode/feode-mcp- Version
- 1.4.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-01
- Updated
- 2026-07-01
- Publisher
- com.feode
- Namespace
- Namespace verified by the MCP Registry via the domain feode.com · how
- Website
- www.feode.com
- Repository
- github.com/FarEastAI/feode-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://www.feode.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- feode-mcp 1.0.0 · protocol 2025-06-18
- Tools discovered
- 12:
get_machining_services,get_machining_terms,submit_machining_rfq,get_company_profile,list_products,get_product_specs,get_certifications,search_capabilities,list_drill_pipe,get_drill_pipe_specs,search_drill_pipe,get_drill_string_guidance - Checked on
- 2026-10-05
How to connect Feode MCP
Feode MCP is a remote MCP server: there is nothing to install. Its endpoint is https://www.feode.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| FeedthroughDebug bridge inside your web app: an agent reads the DOM, console and network. Any browser. | Local · stdio |
| Feishu User PluginFeishu/Lark MCP server + CLI tool. 85 tools, 3 auth layers. Send as user via cookie+protobuf. | Local · stdio |
| Feldspar free repository security scanFree deterministic security scan of public git repos: OSV.dev vulnerable deps, secrets, config lint. | Remote · HTTPLive check: ✓ handshake |
| Fenestra MCPRender and verify native Rust GUIs headlessly: access tree, query, a11y, screenshots, motion. | Local · stdio |
| Feranor ResilienceScan/purge hidden text & score web domains: TLS, DNS, headers, speed. Free scans, $0.01 actions. | Remote · HTTPLive check: ✓ handshake |
| Ferritin - Rust documentationSearch and read Rust documentation for the standard library and any crate on crates.io. | Remote · HTTPLive check: ✓ handshake |
| FetcherThe web capability layer for AI agents: render, extract, DNS, SSL, WHOIS & more via x402. | Remote · HTTPLive check: ✓ handshake |
| FetchSandboxA deterministic verification engine for agents. Proves a fix: fails on the old code, passes on new. | Remote & Local · HTTP, stdioLive check: ✓ handshake |