Skip to content

Dynomatix

by dynomatix.com · remote · no sign-in to list tools · v1.0.0 · published by com.dynomatix

Enquiries for Dynomatix, a software practice.

Final · 1Changes · 2

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

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

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.No findings

    Why it is in this group

    • The name "dynomatix_submit_application" says "submit": a word for a change.
    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 4Claude Code: allow
  • 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.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, 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. It assumes the server is installed as company. Review it before you use it.