Dynomatix
REMOTE · DYNOMATIX.COM · SCANNED AUG 20
Enquiries for Dynomatix, a software practice.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1433 tokens (~204/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (43% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · dynomatix.com
claude mcp add --transport http com-dynomatix-company https://dynomatix.com/mcp
[mcp_servers.com-dynomatix-company] url = "https://dynomatix.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-dynomatix-company": {
"type": "remote",
"url": "https://dynomatix.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-dynomatix-company --url https://dynomatix.com/mcp --transport streamable-http
mcp_servers:
com-dynomatix-company:
url: "https://dynomatix.com/mcp" {
"mcpServers": {
"com-dynomatix-company": {
"type": "http",
"url": "https://dynomatix.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Aug 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Aug 2026 · Probed https://dynomatix.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dynomatix.com | CN=WE1,O=Google Trust Services,C=US | 5 Aug 2026 | 3 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 1a5426c8c05067f213dbf6a9c8fd3ada |
| SANs: dynomatix.com, *.dynomatix.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC secure
Validation of dynomatix.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dynomatix.com. | present | 2371 | 13 | Verified |
| dynomatix.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dynomatix.com/mcp | Verified | 200 | |
| http (plaintext) | http://dynomatix.com/mcp | HTTPS enforced | 301 | https://dynomatix.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
dynomatix_about About Dynomatix ~78
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | object | – | General and hiring email addresses, and the enquiry page. |
| engagements | array | – | The kinds of work Dynomatix takes on. |
| identity | object | – | Name, legal name, URL, tagline, description, founding year. |
| keyPages | array | – | Labelled links to the pages worth reading next. |
| proof | object | – | Years active, products shipped, how many are still live. |
No examples provided.
dynomatix_get_position Read a job posting ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The position's slug, exactly as dynomatix_list_open_positions returned it. Lowercase letters, digits and hyphens. |
No output schema declared.
No examples provided.
dynomatix_get_work Read a case study ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The item's slug, exactly as dynomatix_list_work returned it. Lowercase letters, digits and hyphens. |
No output schema declared.
No examples provided.
dynomatix_list_open_positions List open positions ~95
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| positions | array | yes | Open roles, in the order the site lists them. |
No examples provided.
dynomatix_list_work List past and current work ~109
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| work | array | yes | Products and engagements, in the order the site lists them. |
No examples provided.
dynomatix_submit_application Apply for a position ~518
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The applicant's email address, in the form name@example.com. This is the only way they will be contacted, so check it before sending. | |
| letter | string | – | Optional cover letter. Newlines are preserved. |
| name | string | yes | The applicant's full name. |
| phone | string | – | Optional. The applicant's phone number. |
| portfolio | string | – | Optional. A full web address starting with http:// or https:// — a portfolio, GitHub profile or personal site. |
| position | string | yes | Slug of the role, from dynomatix_list_open_positions. A role that is not on that list is not accepting applications. |
| resume_base64 | string | – | The résumé's bytes, base64-encoded. Use this OR resume_url, never both. Requires resume_filename. Payloads over 5 MB are refused before they are decoded. |
| resume_filename | string | – | Required with resume_base64: it is the only source of the file's extension, which must be one of PDF, DOC or DOCX. Optional with resume_url, where the URL's last path segment is used instead. |
| resume_url | string | – | An https URL that downloads the résumé file directly. Not a sharing or preview page — the response must be the file itself. Use this OR resume_base64, never both. http:// is refused, as are hostnames… |
No output schema declared.
No examples provided.
dynomatix_submit_enquiry Send a work enquiry ~306
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | yes | What needs building, in the enquirer's own words. Newlines are preserved. There is no minimum — a single line is a fine enquiry. |
| company | string | yes | The company or product website. A bare hostname is accepted and https is assumed; anything that is not a web address is refused. |
| string | yes | The enquirer's email address, in the form name@example.com. This is the only address the reply can go to. | |
| name | string | yes | The enquirer's full name. |
| timeline | string | – | Optional. One of: exploring (Exploring), this-quarter (This quarter), already-started (Already started and stuck). Omit it if unknown — blank is valid, a value outside this list is not. |
No output schema declared.
No examples provided.