Skip to content

Dynomatix MCP server

com.dynomatix/companydynomatix.comstreamable-httpv1.0.0Scanned

Enquiries for Dynomatix, a software practice.

7 tools: 1 do something that can't be undone, 2 change things and 4 only read.

Tools: 0 delete, 1 irreversible, 2 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 Dynomatix MCP server can do

The Dynomatix MCP server is published by dynomatix.com, a domain the MCP Registry verified. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (dynomatix_submit_enquiry) and create or change data (2 tools: dynomatix_submit_application and dynomatix_about), but cannot delete data. 4 tools only read.

1 tool can send data out of your system (dynomatix_submit_application).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.0.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.

7 tools

Can't be undone 1Claude Code: ask
  • dynomatix_submit_enquirySend a project enquiry to Dynomatix — the same form the site's enquiry page submits.No findings

    Why it is in this group

    • The name "dynomatix_submit_enquiry" 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.
    Description, as the server wrote it
    Send a project enquiry to Dynomatix — the same form the site's enquiry page submits. This is final: it delivers straight to a monitored human inbox and cannot be edited, recalled or deleted afterwards. Confirm the details with the person you are acting for before you call it, and do not call it twice for the same submission — a retry sends a second copy. Give the company or product website in `company` (a bare hostname like example.com is fine) and say what needs building in `brief`. Nothing is stored: the enquiry becomes an email and nothing else. Ask for a budget on the call, not here — this form does not collect one.
Changes things 2Claude Code: ask
  • dynomatix_aboutWho Dynomatix is, what it sells and how to reach it.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
    Who Dynomatix is, what it sells and how to reach it. Returns the company's identity and tagline, its engagement types, both contact addresses, its key pages and its track record. Read this first if you are deciding whether this company fits a need; use dynomatix_submit_enquiry to start a conversation. Takes no arguments.
  • dynomatix_submit_applicationSubmit a job application to Dynomatix, résumé included.Can send data outNo findings

    Why it is in this group

    • The name "dynomatix_submit_application" says "submit": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Submit a job application to Dynomatix, résumé included. This is final: it delivers straight to a monitored human inbox and cannot be edited, recalled or deleted afterwards. Confirm the details with the person you are acting for before you call it, and do not call it twice for the same submission — a retry sends a second copy. Set `position` to a slug from dynomatix_list_open_positions. Supply the résumé exactly one of two ways: `resume_url`, an https link that downloads the file itself (a sharing page from a drive or a document service is not a direct link and will be refused), or `resume_base64` together with `resume_filename`. Supplying both, or neither, is refused. The résumé must be a PDF, DOC or DOCX file under 5 MB; its contents are checked against its extension, so a renamed file is refused too. Nothing is stored until every field passes, and the reply confirms receipt with a submission id worth quoting in any follow-up — it never returns the résumé or a link to it.
Only reads 4Show 4 read-only tools
  • dynomatix_get_positionRead one job posting in full: responsibilities, requirements and how the role is set up.No findings

    Why it is in this group

    • The name "dynomatix_get_position" says "get": a word for reading.
    Description, as the server wrote it
    Read one job posting in full: responsibilities, requirements and how the role is set up. Returns the posting's own markdown, frontmatter included — the title and canonical URL it opens with are the citation to quote when you tell someone about the role. Call dynomatix_list_open_positions first to get a valid slug; a slug that is not currently open is refused rather than guessed at.
  • dynomatix_get_workRead one case study in full: what the problem was, what was built and what it changed.No findings

    Why it is in this group

    • The name "dynomatix_get_work" says "get": a word for reading.
    Description, as the server wrote it
    Read one case study in full: what the problem was, what was built and what it changed. Returns the study's own markdown, frontmatter included — the title and canonical URL it opens with are the citation to quote. Call dynomatix_list_work first for a valid slug; only entries whose `caseStudyUrl` is not null have a write-up to return.
  • dynomatix_list_open_positionsList every role Dynomatix is currently hiring for.No findings

    Why it is in this group

    • The name "dynomatix_list_open_positions" says "list": a word for reading.
    Description, as the server wrote it
    List every role Dynomatix is currently hiring for. Returns one entry per position with its slug, title, one-line summary, employment type, canonical URL and posting dates. Start here before dynomatix_get_position or dynomatix_submit_application: the slug this returns is the value both of them expect. An empty list means there are no openings right now, not that the lookup failed. Takes no arguments.
  • dynomatix_list_workList the products and client work Dynomatix has shipped.No findings

    Why it is in this group

    • The name "dynomatix_list_work" says "list": a word for reading.
    Description, as the server wrote it
    List the products and client work Dynomatix has shipped. Returns one entry per item with its name, the year it started, its status, a short description and its links. Retired items are included — the site shows them and `status` says which is which — because a track record with the failures removed is not a track record. Where `caseStudyUrl` is not null, dynomatix_get_work will return the full write-up for that slug. Takes no arguments.

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:37 UTC, unchanged since Oct 22, 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
3
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 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://dynomatix.com/mcp: tools/list returned 7 tools to an anonymous client, including dynomatix_submit_enquiry (irreversible), dynomatix_submit_application (write), dynomatix_about (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http company https://dynomatix.com/mcp
claude mcp add --transport http company https://dynomatix.com/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__company__dynomatix_list_open_positions",
      "mcp__company__dynomatix_get_position",
      "mcp__company__dynomatix_list_work",
      "mcp__company__dynomatix_get_work"
    ],
    "ask": [
      "mcp__company__dynomatix_submit_application",
      "mcp__company__dynomatix_submit_enquiry",
      "mcp__company__dynomatix_about"
    ],
    "deny": []
  }
}

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 company. Review it before you use it.

Capability tags behind 1 rule
  • mcp__company__dynomatix_submit_application outbound

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.dynomatix/company/verify?hash=00bd9a5aecdf7f68dfb7317c567de870a9793777ffc34b1dd7a11d58b6dd9cfd" | jq -e '.changed == false'

Pinned hash 00bd9a5aecdf, from Nov 13, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.dynomatix/company/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.dynomatix/company
[![Anlyon Radar](https://radar.anlyon.com/badge/com.dynomatix/company.svg)](https://radar.anlyon.com/servers/com.dynomatix/company)

Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.

Dynomatix MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Dynomatix MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 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 Dynomatix MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Dynomatix MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: dynomatix_submit_enquiry.

What tools does the Dynomatix MCP server have?

7 tools: 1 irreversible, 2 write, 4 read. dynomatix_submit_enquiry, dynomatix_submit_application, dynomatix_about, dynomatix_list_open_positions, dynomatix_get_position, dynomatix_list_work and dynomatix_get_work.

Does the Dynomatix MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Dynomatix MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): dynomatix_submit_application.

Has the Dynomatix MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.