Feode MCP: MCP server, setup and security

What Feode MCP does

According to its repository: “Query FEODE offshore oilfield services: well plug and abandonment, subsea wellheads, continuous circulation drilling and a drill-string spec reference.”

The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Feode MCP is listed under Other integrations, a category of 194 servers in the directory, where it ranks #190 by stars.

Installing and connecting Feode MCP

Distribution modes declared in the official MCP registry:

• remote server (streamable-http): you connect to it by URL, with nothing to install locally

It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: TypeScript.

Security: what to check

Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Feode MCP. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on June 22, 2026, the FarEastAI/feode-mcp repository has 1 stars and 0 forks, with 0 open issues. It has more stars than 7% of the servers in the directory. Last change 3 months ago. Version published in the registry: 1.4.0 (July 1, 2026).

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.