_ registry / mcp + a2a streamable-http · checked 2h ago

feode-mcp

https://www.feode.com

Registry code: a1ca5583f8bc4185

api record

FEODE (Shenzhen Far East Oil Drilling Engineering) capability server. Call tools/list, then tools/call. Covers offshore well abandonment, subsea wellhead (BV+CCS classed), continuous circulation drilling, drill pipe, fishing, supervision.

endpoint
https://www.feode.com/mcp
door code
7fe0e2360940cab9
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is feode-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is feode-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does feode-mcp have?
12 tools: submit_machining_rfq, get_machining_services, get_machining_terms, get_drill_pipe_specs, list_products, search_capabilities, get_certifications, search_drill_pipe, ….
Is feode-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.8%

90 days 99.1%· all time 99.2%

latency
432ms

last good check

priced tools
0

of 12 tools

_ answered our checks, 90 days 1022 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • degraded → live
_ what it is for
topic
energy & utilities oil & gas
used for
  • get company certifications
  • get company profile
  • get drill pipe specifications
  • get drill string guidance
  • get machining services capabilities
takes → gives
text, data → data
tools
11 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 12 tools
11 open 1 never probed 11 of 12 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_machining_services reads open 19h ago

    FEODE AI-accessible precision contract machining & testing: capabilities (large-envelope CNC, deep-hole boring up to 7m, non-magnetic drill collar repair, welding/cladding), test capacity (30k psi hydraulic, 20k psi N2, MPI/UT/PT), materials, how-it-works, payment & compliance policy. FEODE machines to the client's drawing/spec and ships internationally. Compliance-first, prepayment-based.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_machining_terms reads open 19h ago

    Full intake terms & compliance requirements for FEODE's machining/testing service: required RFQ fields, KYB-lite (legal entity / country / real contact), end-use declaration, prohibited items, IP & liability terms, prepayment & accepted payment methods (bank wire / T/T).

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_drill_pipe_specs reads open 11h ago

    Full NOV Grant Prideco performance specs for one drill string item by id: pipe-body new/premium torsional & tensile yield, internal pressure, collapse; tool-joint OD/ID, make-up torque max/min, drift, torsional yield. Use list_drill_pipe for ids.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Item id, e.g. dp-5-19.50-s135-nc50"
    }
  }
}
    arguments 12 lines
  • list_products reads open 21h ago

    List FEODE's 7 product/service lines (id, name, category).

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • search_capabilities reads open 9h ago

    Keyword search across FEODE products/specs. e.g. 'subsea wellhead 15000 psi', 'one trip abandonment', 'continuous circulation'.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • get_certifications reads open 21h ago

    FEODE certifications: BV + CCS classification of the subsea wellhead system (incl. references), 8 API monogram licenses, ISO 9001/14001/45001, national awards.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • search_drill_pipe reads open 9h ago

    Keyword search the NOV Grant Prideco drill string reference (e.g. 'NC50', '5 S-135', 'HT55 make-up torque', '8 drill collar', 'XT57'). Returns matching items with full specs.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • list_drill_pipe reads open 11h ago

    List all NOV Grant Prideco drill string items in the reference DB (drill pipe, heavy-weight drill pipe HWDP, drill collars) with id, label, product_type, connection, grade.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_product_specs reads open 11h ago

    Detailed specs/highlights for one product line by id.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "One of: well-abandonment, subsea-wellhead, feccs, completion, drill-pipe, fishing, supervision"
    }
  }
}
    arguments 12 lines
  • get_drill_string_guidance reads open 19h ago

    NOV Grant Prideco drill-string guidance & reference data (from the Grant Prideco 钻具技术手册, excerpted from API Spec 7 / API RP 7G): make-up torque practice (incl. the 80% drilling-torque rule), handling/grip distance, care & handling, sour service; double-shoulder connection families HT/XT/XT-M/GPDS with recommended make-up torque & thread forms; drill-pipe steel grades & API tool joints; heavy-weight drill pipe (3 types + dimensional data); drill collars (material, bending-strength-ratio, weight, connection selection, ideal size by hole); rotary-shouldered connection interchangeability; kelly (square/hex weights & connections); crossover/service subs; well control (kill/pressure formulas, pump output, capacity & displacement, buoyancy factor); and imperial-to-SI unit conversions. ALSO includes reference_tables: the manual's dense spec/torque/weight/capacity/inspection matrices and BSR charts as reference IMAGE URLs (including the wide cross-page drill-collar make-up-torque & weight tables assembled whole from the facing-page scan) — for exact cell values, return the matching image_url to the user instead of transcribing the numbers. Call without a topic to get everything, or pass one topic.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "description": "Optional: make_up_torque | handling | care_and_handling | double_shoulder_connections | sour_service | field_usage | premium_connections | pipe_grades_and_body | heavy_weight_drill_pipe | drill_collars | connection_interchange | kelly | crossover_subs | well_control | unit_conversion | reference_tables (dense spec/torque/weight/capacity/inspection matrices & BSR charts as reference image URLs)"
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • get_company_profile reads open 21h ago

    FEODE company profile: legal name, founding year (1985), HQ, Huizhou manufacturing/test base, areas served, contact.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • submit_machining_rfq changes data unknown never probed

    Submit a structured machining/testing RFQ. Runs a lightweight compliance screen (prohibited-use + sanctions) and, if cleared, registers the enquiry for human follow-up from [email protected]. Not a contract or quotation; no payment is taken here. You must provide the legal entity behind the request.

    mcp-tool

    {
  "type": "object",
  "required": [
    "company",
    "country",
    "contact_name",
    "email",
    "part_description",
    "material",
    "quantity",
    "end_use"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "Contact email"
    },
    "notes": {
      "type": "string",
      "description": "Any other details (optional)"
    },
    "company": {
      "type": "string",
      "description": "Legal entity name placing the order"
    },
    "country": {
      "type": "string",
      "description": "Country of registration of the legal entity"
    },
    "end_use": {
      "type": "string",
      "description": "Declared end-use of the part"
    },
    "industry": {
      "type": "string",
      "description": "Industry sector"
    },
    "material": {
      "type": "string",
      "description": "Material / grade"
    },
    "quantity": {
      "type": "string",
      "description": "Quantity"
    },
    "tolerance": {
      "type": "string",
      "description": "Key tolerances (optional)"
    },
    "drawing_url": {
      "type": "string",
      "description": "Link to drawing/spec if available (optional)"
    },
    "contact_name": {
      "type": "string",
      "description": "Real human contact name"
    },
    "part_description": {
      "type": "string",
      "description": "Part/component description or drawing reference"
    }
  },
  "additionalProperties": true
}
    arguments 64 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a1ca5583f8bc4185.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a1ca5583f8bc4185/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a1ca5583f8bc4185/badge.svg)](https://brick.blue/agent/a1ca5583f8bc4185?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.