AMJ Tools
REMOTE · FACTORY.AMJTECH.OM:9443
Pay-per-call tools for AI agents: product photos, documents, web pages, data. USDC via x402.
Available components
Last scanned (28 minutes ago)
Scores higher than 53% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category AI and Machine Learning
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 → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.13 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 2 Nov 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.
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 65
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 5 Nov 2026 · Probed https://factory.amjtech.om:9443/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of factory.amjtech.om. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| om. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://factory.amjtech.om:9443/mcp | Unreachable | ||
| http (plaintext) | http://factory.amjtech.om/mcp | HTTPS enforced | 308 | https://factory.amjtech.om/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_tool Get tool details ~36
Input JSON Schema, output description, examples, limits and prices for one tool.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Tool slug from list_tools |
No output schema declared.
No examples provided.
list_tools List tools ~29
Every live tool with its slug, purpose, category, price per call (USDC) and endpoint.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_tool Run a tool ~120
Run a tool on an input matching its input schema (see get_tool). Pay with payment_signature (x402 v2) or a pass api_key. Without either, returns HTTP 402 with payment_required describing the USDC payment.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | API key of a 30-day pass for this tool. |
| input | object | yes | Request body matching the tool input schema. |
| payment_signature | string | – | x402 v2 PAYMENT-SIGNATURE value for this call. |
| slug | string | yes | Tool slug from list_tools |
No output schema declared.
No examples provided.
How do I install the AMJ Tools MCP server?
AMJ Tools is a hosted endpoint at https://factory.amjtech.om:9443/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · factory.amjtech.om:9443
claude mcp add --transport http om-amjtech-tools 'https://factory.amjtech.om:9443/mcp'
What is the AMJ Tools MCP server?
AMJ Tools is an MCP server listed in the public MCP registry as om.amjtech/tools. Pay-per-call tools for AI agents: product photos, documents, web pages, data. USDC via x402. This page covers its hosted endpoint (https://factory.amjtech.om:9443/mcp).
Is the AMJ Tools MCP server safe to use?
AMJ Tools scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AMJ Tools MCP server expose?
AMJ Tools exposes 3 tools: list_tools, get_tool, run_tool. Their descriptions and schemas cost roughly 185 tokens of context every time the server is loaded.
Does the AMJ Tools MCP server require authentication?
Its publisher declares no required credentials for AMJ Tools. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the AMJ Tools MCP server still maintained?
AMJ Tools is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.