Chamfer: CNC machining, molding, sheet metal and PCB RFQs; MRO parts by part num… MCP server
com.forevenza.services/chamferservices.forevenza.comstreamable-httpv1.1.0Scanned
RFQs shops can quote for machined, molded, sheet metal and PCB parts; MRO parts by part number.
19 tools: 1 can delete or cancel things, 4 do something that can't be undone, 9 change things and 5 only read.
- Reads private data · 2
- Reads text others write · 2
- Can send data out · 2
- 6 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 4 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Chamfer: CNC machining, molding, sheet metal and PCB RFQs; MRO parts by part num… MCP server can do
The Chamfer: CNC machining, molding, sheet metal and PCB RFQs; MRO parts by part num… MCP server is published by services.forevenza.com, a domain the MCP Registry verified. It has 19 tools. It can delete or cancel things (1 tool: decline_offer), do things that cannot be undone, such as sending, paying or publishing (submit_request, send_requirement, release_payment and submit_purchase_order) and create or change data (9 tools: interpret_requirement, edit_requirement, request_status, accept_offer and 5 more). 5 tools only read.
2 tools read private data (inspect_offer and report_vendor_status); 2 tools bring in text other people can write (describe_proposition and inspect_offer); 2 tools can send data out of your system (submit_request and send_requirement). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 6 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 17, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
19 tools
Deletes or cancels 1Claude Code: deny
decline_offerDecline an issued offer on its inspected terms.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Decline an issued offer on its inspected terms.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Can't be undone 4Claude Code: ask
release_paymentConfirm a payment condition only where the inspected order allows the customer to release it.No findings
Why it is in this group
- The name "release_payment" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Confirm a payment condition only where the inspected order allows the customer to release it. This records approval; it does not pay the processor.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
send_requirementSend the requirement to Chamfer once the buyer says to: the first send records the request (its receipt token is the requirement's token, for request_status and offers); a later se…Can send data outNo findings
Why it is in this group
- The name "send_requirement" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "send_requirement" says "send": it sends or publishes something to other people.
Description, as the server wrote it Send the requirement to Chamfer once the buyer says to: the first send records the request (its receipt token is the requirement's token, for request_status and offers); a later send of a changed requirement records a revision of the same request. Name the revision the buyer saw. This orders nothing: an offer comes later and is accepted separately on its exact terms.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
submit_purchase_orderSend the buyer's purchase order for an issued offer or a placed order: number, revision, lines, total, currency and payment terms.No findings
Why it is in this group
- The name "submit_purchase_order" says "submit": a word for a change.
- The name "submit_purchase_order" also says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Send the buyer's purchase order for an issued offer or a placed order: number, revision, lines, total, currency and payment terms. It is matched against the accepted terms; differences are recorded and shown in inspect_offer thread.purchasing as exceptions, never silently accepted. A changed purchase order is the same number with a higher revision. This does not accept the offer and pays nothing.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
submit_requestSend a requirement to Chamfer (Manufacturing quotes: machining, molding, sheet metal and PCB assembly; Industrial equipment and MRO parts by part number or model).Can send data outNo findings
Why it is in this group
- The name "submit_request" says "submit": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
- The input carries an amount (input.budget.amount) and a currency, so it moves money.
- The input addresses people (input.geography.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.geography.to): what the tool writes goes there.
Description, as the server wrote it Send a requirement to Chamfer (Manufacturing quotes: machining, molding, sheet metal and PCB assembly; Industrial equipment and MRO parts by part number or model). It is recorded and answered with a receipt: keep its id and token to read the request's status (request_status), to add details later (continuation), and to act on an offer made in reply. A requirement is not an order and costs nothing; nothing is bought until an offer's exact terms are accepted.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 9Claude Code: ask
accept_offerPlace an order on terms you have inspected and the buyer has authorized you to accept.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Place an order on terms you have inspected and the buyer has authorized you to accept. Requires the exact terms hash and explicit acceptance. Follow inspect_offer later for payment links and verified payment state.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
answer_remedyAccept or decline a remedy the business proposed on a placed order (inspect_offer thread.fulfilment.remedies with state PROPOSED).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Accept or decline a remedy the business proposed on a placed order (inspect_offer thread.fulfilment.remedies with state PROPOSED). Recorded for the business, which applies it and shows the result there. Accepting a credit or refund here moves no money; the business records it when its payment processor does.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
counter_offerPropose a change to an issued offer on its inspected terms: other quantities (by item index in terms.items), another list of companies (where the items price companies), a delivery…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Propose a change to an issued offer on its inspected terms: other quantities (by item index in terms.items), another list of companies (where the items price companies), a delivery date, a total price for the whole, a payment plan, or a note. It is a proposal, not a change: the terms stand and can still be accepted as they are. The business answers it in inspect_offer thread.counteroffers, with a revised offer to inspect and accept, or a reason. A later proposal replaces an earlier one still awaiting an answer. Nothing here orders or pays.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
edit_requirementSet fields by name ({"op":"set","values":{...}}, an empty value clears) or change the list ({"op":"add"|"update"|"remove"|"replace", ...}), exactly as given: no reading.No findings
Why it is in this group
- The name "edit_requirement" says "edit": a word for a change.
Description, as the server wrote it Set fields by name ({"op":"set","values":{...}}, an empty value clears) or change the list ({"op":"add"|"update"|"remove"|"replace", ...}), exactly as given: no reading. Use it to answer the open question when the answer is a value.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
inspect_deliveryRecord the buyer's inspection of a placed order: for each item (its index in terms.items) the quantity accepted and the quantity rejected, with a reason for a rejection, optionally…1 finding
Why it is in this group
- The name "inspect_delivery" says "inspect": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "inspect_delivery" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "inspect_delivery" says "inspect": a word for reading.
Description, as the server wrote it Record the buyer's inspection of a placed order: for each item (its index in terms.items) the quantity accepted and the quantity rejected, with a reason for a rejection, optionally for one portion of the order. Whether it was accepted is computed: only when nothing is rejected. Recorded for the business, which answers a rejection in inspect_offer thread.fulfilment, with a proposed remedy. Nothing here pays or refunds.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
interpret_requirementGive Chamfer the buyer's requirement, or a correction or addition to it, in their own words: it is read into a structured requirement (each value says which words it came from), co…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Give Chamfer the buyer's requirement, or a correction or addition to it, in their own words: it is read into a structured requirement (each value says which words it came from), conflicting or unclear facts come back as one question, and words not yet read are kept as written. Pass the requirement (id, token) from the first answer to continue it. Nothing is sent or ordered: send_requirement sends it when the buyer says so. When you already have the fields in structured form, use submit_request instead.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
report_vendor_statusReport the seller's vendor standing with the buyer's organization (APPROVED, DOCUMENTS_REQUESTED or REJECTED) with the buyer's approval or case reference and any documents requeste…Reads private data1 finding
Why it is in this group
- The name "report_vendor_status" says "status": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- private-dataThe description's first sentence says "document": it reads documents.
Findings
- Warn
The server marks "report_vendor_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "report_vendor_status" says "status": a word for reading.
Description, as the server wrote it Report the seller's vendor standing with the buyer's organization (APPROVED, DOCUMENTS_REQUESTED or REJECTED) with the buyer's approval or case reference and any documents requested. Recorded as the buyer's own statement; the business answers it in inspect_offer thread.purchasing.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
request_statusResume a requirement using the receipt credentials.2 findings
Why it is in this group
- The name "request_status" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "Resume a requirement using the receipt credentials. Read the recorded requirement, any rep..."
- Warn
The server marks "request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "request_status" says "request": a word for a change.
Description, as the server wrote it Resume a requirement using the receipt credentials. Read the recorded requirement, any replies the business has published on it (messages: where it answers a buyer with no email, it answers here) and any linked offers. Answer a reply by sending a continuation. Contact details are kept apart.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
state_purchasing_requirementsTell the business how the buyer's purchasing works for this offer: whether the seller must be an approved vendor, whether a purchase order is required, which documents are needed, …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Tell the business how the buyer's purchasing works for this offer: whether the seller must be an approved vendor, whether a purchase order is required, which documents are needed, the seller's vendor id with the buyer, where orders and invoices go, and the payment terms. Recorded as the buyer's statement; the business answers it in inspect_offer thread.purchasing. Nothing here orders or pays.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 5Show 5 read-only tools
describe_propositionEverything about one Chamfer service, by the slug list_propositions gives: what happens to a request, what you receive, its price basis (never an offer), when a reply is due, who t…Reads text others writeNo findings
Why it is in this group
- The name "describe_proposition" says "describe": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "reply": it reads comments, which other people can write.
Description, as the server wrote it Everything about one Chamfer service, by the slug list_propositions gives: what happens to a request, what you receive, its price basis (never an offer), when a reply is due, who the buyer contracts with and who invoices, scope and limits, the request fields with examples, and the lookups it runs.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_requirementA Chamfer requirement as it stands: each value with where it came from, what it replaced, the open question, words not yet read, whether it was sent and any offer on it.No findings
Why it is in this group
- The name "get_requirement" says "get": a word for reading.
Description, as the server wrote it A Chamfer requirement as it stands: each value with where it came from, what it replaced, the open question, words not yet read, whether it was sent and any offer on it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
inspect_offerRead the exact authorized terms, terms hash, order state and processor payment links, and the thread the business published on the offer: its answers to counteroffers (thread.count…Reads private dataReads text others write1 finding
Why it is in this group
- The name "inspect_offer" says "inspect": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "thread": it reads messages.
- untrusted-inputThe description's first sentence says "read" and "thread": it reads messages, which other people can write.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...(thread.fulfilment). Use the offer link credentials, or credentials of the request explicit..."
Description, as the server wrote it Read the exact authorized terms, terms hash, order state and processor payment links, and the thread the business published on the offer: its answers to counteroffers (thread.counteroffers), the purchasing requirements, vendor status and purchase order matches it holds (thread.purchasing), and the portions, shortfall and remedies of delivery (thread.fulfilment). Use the offer link credentials, or credentials of the request explicitly linked to this offer.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_propositionsList Chamfer's services (Manufacturing quotes: machining, molding, sheet metal and PCB assembly; Industrial equipment and MRO parts by part number or model): each one's slug, a one…No findings
Why it is in this group
- The name "list_propositions" says "list": a word for reading.
Description, as the server wrote it List Chamfer's services (Manufacturing quotes: machining, molding, sheet metal and PCB assembly; Industrial equipment and MRO parts by part number or model): each one's slug, a one-line summary, and whether it runs instantly as a lookup or takes a requirement you send.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
retrieve_deliverableRetrieve what a paid order delivers, where the business produces it itself (a report): the exact text, its SHA-256, version, sources and any shortfall.1 finding
Why it is in this group
- The name "retrieve_deliverable" says "retrieve": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...e. Use the offer link or linked request credentials."
Description, as the server wrote it Retrieve what a paid order delivers, where the business produces it itself (a report): the exact text, its SHA-256, version, sources and any shortfall. Before payment is confirmed it says it is not yet available. Use the offer link or linked request credentials.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
8 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__chamfer__send_requirement",
"mcp__chamfer__submit_request"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:22 UTC, unchanged since Nov 12, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 14
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 14 tools that change things (1 destructive, 4 irreversible, 9 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://chamfer.forevenza.com/mcp: tools/list returned 19 tools to an anonymous client, including decline_offer (destructive), submit_request (irreversible), send_requirement (irreversible), release_payment (irreversible), submit_purchase_order (irreversible) and 9 more
Posture changes
- Nov 12, 2026
- Tools that change things, listed without credentials: 1 to 14
Findings
Matches of fixed checks, with the text they matched.
- Warnrequest_status
The server marks "request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "request_status" says "request": a word for a change.
The server marks "report_vendor_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "report_vendor_status" says "status": a word for reading.
- Warninspect_delivery
The server marks "inspect_delivery" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "inspect_delivery" says "inspect": a word for reading.
- Inforequest_status
The description mentions "credentials".
What this check looks forMatched text
description: "Resume a requirement using the receipt credentials. Read the recorded requirement, any rep..."
- Infoinspect_offer
The description mentions "credentials".
What this check looks forMatched text
description: "...(thread.fulfilment). Use the offer link credentials, or credentials of the request explicit..."
The description mentions "credentials".
What this check looks forMatched text
description: "...e. Use the offer link or linked request credentials."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools16 added, 3 changed.+16 added~3 changedView diff
- Added:accept_offerChanges things
- Added:answer_remedyChanges things
- Added:counter_offerChanges things
- Added:decline_offerDeletes or cancels
- Added:edit_requirementChanges things
- Added:get_requirementOnly reads
- Added:inspect_deliveryChanges things
- Added:inspect_offerOnly reads
- Added:interpret_requirementChanges things
- Added:release_paymentCan't be undone
- Added:report_vendor_statusChanges things
- Added:request_statusChanges things
- Added:retrieve_deliverableOnly reads
- Added:send_requirementCan't be undone
- Added:state_purchasing_requirementsChanges things
- Added:submit_purchase_orderCan't be undone
- Changed:describe_propositionOnly readstitledescriptioninputSchema
- Changed:list_propositionsOnly readsdescription
- Changed:submit_requestCan't be undonedescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 14.View diff
- Tools that change things, listed without credentials: 1 to 14
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http chamfer https://chamfer.forevenza.com/mcpclaude mcp add --transport http chamfer https://chamfer.forevenza.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__chamfer__list_propositions",
"mcp__chamfer__describe_proposition",
"mcp__chamfer__get_requirement",
"mcp__chamfer__inspect_offer",
"mcp__chamfer__retrieve_deliverable"
],
"ask": [
"mcp__chamfer__submit_request",
"mcp__chamfer__interpret_requirement",
"mcp__chamfer__edit_requirement",
"mcp__chamfer__send_requirement",
"mcp__chamfer__request_status",
"mcp__chamfer__accept_offer",
"mcp__chamfer__release_payment",
"mcp__chamfer__counter_offer",
"mcp__chamfer__submit_purchase_order",
"mcp__chamfer__state_purchasing_requirements",
"mcp__chamfer__report_vendor_status",
"mcp__chamfer__inspect_delivery",
"mcp__chamfer__answer_remedy"
],
"deny": [
"mcp__chamfer__decline_offer"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as chamfer. Review it before you use it.
Capability tags behind 5 rules
- mcp__chamfer__describe_proposition untrusted-input
- mcp__chamfer__submit_request outbound
- mcp__chamfer__send_requirement outbound
- mcp__chamfer__inspect_offer private-data, untrusted-input
- mcp__chamfer__report_vendor_status private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.forevenza.services/chamfer/verify?hash=e5868085222ffb5a7b4c797edc941e3633c3935fdf370a97cd03b1dd9634af71" | jq -e '.changed == false'Pinned hash e5868085222f, from Nov 17, 2026, 20:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.forevenza.services/chamfer/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.forevenza.services/chamfer)Source: MCP Registry. Synced Nov 4, 2026, 05:17 UTC.
Chamfer: CNC machining, molding, sheet metal and PCB RFQs; MRO parts by part num… MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Chamfer: CNC machining, molding, sheet metal and PCB RFQs; MRO parts by part num… MCP server safe?
- No scan can promise that. What its definitions show: 19 tools, 14 of which can change, send or delete something, and 6 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Chamfer: CNC machining, molding, sheet metal and PCB RFQs; MRO parts by part num… MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: decline_offer.
Can the Chamfer: CNC machining, molding, sheet metal and PCB RFQs; MRO parts by part num… MCP server do things that cannot be undone?
- Yes. 4 tools can send, pay, publish or merge: submit_request, send_requirement, release_payment and submit_purchase_order.
What tools does the Chamfer: CNC machining, molding, sheet metal and PCB RFQs; MRO parts by part num… MCP server have?
- 19 tools: 1 destructive, 4 irreversible, 9 write, 5 read. decline_offer, submit_request, send_requirement, release_payment, submit_purchase_order, interpret_requirement, edit_requirement, request_status and 11 more.
Does the Chamfer: CNC machining, molding, sheet metal and PCB RFQs; MRO parts by part num… MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Chamfer: CNC machining, molding, sheet metal and PCB RFQs; MRO parts by part num… MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): submit_request and send_requirement.
Has the Chamfer: CNC machining, molding, sheet metal and PCB RFQs; MRO parts by part num… MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.