SwishrJobs
REMOTE · SWISHRJOBS.COM
Deterministic digital jobs with independently verified deliverables.
Available components
Last scanned (10 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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 Security57
- 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 5 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 27462 tokens (~240/item across 114 items; 114 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 114 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Schema quality: 23739 → 27462 ▼ functional
- New tool “submit_accessibility_conformance_audit” functional
- New tool “submit_commerce_conformance_suite” functional
- New tool “submit_compliance_evidence_pack” functional
- New tool “submit_compliance_readiness_pack” functional
- New tool “submit_data_migration_readiness_pack” functional
- New tool “submit_openapi_conformance_check” functional
- New tool “submit_release_readiness_gate” functional
- New tool “submit_security_audit_pack” functional
- New tool “submit_security_hardening_audit” functional
- New tool “submit_settlement_reliability_report” functional
- New tool “submit_statistics_plan_checker” functional
- New tool “submit_supply_chain_licence_audit” functional
- New tool “submit_webhook_signature_verify” functional
- New tool “submit_x402_endpoint_preflight” functional
- 4 Nov 26 +1
- Tool “submit_unit_conversion_library” rewrote its description, which is the text the model reads security
- Schema quality: 9834 → 23739 ▼ functional
- Destructive annotations: pass → 100 functional
- New tool “submit_a2a_card_validator” functional
- New tool “submit_agent_cost_attribution” functional
- New tool “submit_agent_trace_analyser” functional
- New tool “submit_api_contract_diff” functional
- New tool “submit_backtest_overfitting_check” functional
- New tool “submit_bank_statement_reconciler” functional
- New tool “submit_cli_tool_scaffold” functional
- New tool “submit_cron_expression_check” functional
- New tool “submit_csv_column_profile” functional
- New tool “submit_csv_date_normalise” functional
- New tool “submit_csv_deduplicate” functional
- New tool “submit_csv_dialect_report” functional
- New tool “submit_csv_missing_value_report” functional
- New tool “submit_dashboard_spec_from_questions” functional
- New tool “submit_data_lineage_graph” functional
- New tool “submit_database_migration_review” functional
- New tool “submit_dbt_test_generation” functional
- New tool “submit_dependency_vulnerability_triage” functional
- New tool “submit_dq_rules_generator” functional
- New tool “submit_embedding_similarity_report” functional
- New tool “submit_env_file_check” functional
- New tool “submit_eval_dataset_builder” functional
- New tool “submit_expense_policy_checker” functional
- New tool “submit_feature_flag_audit” functional
- New tool “submit_financial_ratio_report” functional
- New tool “submit_fine_tune_data_formatter” functional
- New tool “submit_fx_rate_normaliser” functional
- New tool “submit_guardrail_policy_config” functional
- New tool “submit_iban_bic_validator” functional
- New tool “submit_invoice_data_extraction” functional
- New tool “submit_iso20022_validator” functional
- New tool “submit_json_key_audit” functional
- New tool “submit_json_ndjson_check” functional
- New tool “submit_kpi_definition_catalogue” functional
- New tool “submit_kubernetes_manifest_hardening” functional
- New tool “submit_ledger_integrity_check” functional
- New tool “submit_llm_output_schema_guard” functional
- New tool “submit_log_format_parser” functional
- New tool “submit_mcp_tool_schema_linter” functional
- New tool “submit_model_card_generator” functional
- New tool “submit_multi_agent_orchestration_plan” functional
- New tool “submit_ohlcv_gap_checker” functional
- New tool “submit_package_manifest_check” functional
- New tool “submit_parquet_partition_planner” functional
- New tool “submit_pci_scope_mapper” functional
- New tool “submit_portfolio_risk_report” functional
- New tool “submit_prompt_regression_suite” functional
- New tool “submit_rag_chunking_plan” functional
- New tool “submit_requirements_pin_check” functional
- New tool “submit_sepa_payment_file_builder” functional
- New tool “submit_sql_to_dataframe_migration” functional
- New tool “submit_star_schema_designer” functional
- New tool “submit_strategy_rule_compiler” functional
- New tool “submit_terraform_module_review” functional
- New tool “submit_time_series_anomaly_config” functional
- New tool “submit_token_cost_estimator” functional
- New tool “submit_tool_permission_matrix” functional
- New tool “submit_trade_blotter_reconciler” functional
- New tool “submit_url_health_matrix” functional
- New tool “submit_vat_tax_calculator” functional
- New tool “submit_x402_endpoint_audit” functional
- 3 Nov 26 0
- New tool “submit_unit_conversion_library” functional
- 2 Nov 26 +1
- New tool “submit_json_to_csv_rows” functional
- 1 Nov 26 0
- Tool “select_capability” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “select_capability” reworded the description of “task” cosmetic
- 31 Oct 26 58
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://swishrjobs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=swishrjobs.com | CN=WE1,O=Google Trust Services,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | be687ad1048b3c480ec82fb230ffdb6c |
| SANs: swishrjobs.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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of swishrjobs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| swishrjobs.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://swishrjobs.com/mcp | Verified | 200 | |
| http (plaintext) | http://swishrjobs.com/mcp | HTTPS enforced | 301 | https://swishrjobs.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. 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 →
submit_webhook_signature_verify Webhook signature verification ~229
Verify an inbound webhook HMAC signature against the raw body and secret, and flag a replay-window breach. At the start of a webhook handler, before acting on the event. Do not choose this when the sender uses a public-key scheme, which needs its key. Example requests: Verify this webhook signature before I trust the event. | Is this webhook payload authentic? | Check this Stripe/GitHub webhook signature. | Did this webhook come from the real sender?
| Name | Type | Req | Description |
|---|---|---|---|
| accepted_price | string|number | – | The amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optiona… |
| authorized_by | string | yes | Identifier of the human or agent authorizing this job. |
| inputs | object | yes | – |
| quote_id | string | – | The quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued. |
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Per-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job. |
| artifacts | array | – | – |
| capability_id | string | – | – |
| job_id | string | yes | – |
| quote | object | – | – |
| state | – | yes | – |
| verification | object | – | Independent verification. verification.ok = false means the job failed, not a partial success. |
No examples provided.
submit_x402_endpoint_audit x402 endpoint audit ~222
Audit an x402 endpoint URL for HTTPS, host, query-string and path problems that affect catalogs and payments. Before listing an x402 endpoint in a facilitator catalog. Do not choose this when you need the live 402 challenge verified, which needs a request. Example requests: Audit this x402 endpoint URL. | Is my x402 resource URL well formed for a facilitator? | Check this endpoint for payment-catalog problems.
| Name | Type | Req | Description |
|---|---|---|---|
| accepted_price | string|number | – | The amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optiona… |
| authorized_by | string | yes | Identifier of the human or agent authorizing this job. |
| inputs | object | yes | – |
| quote_id | string | – | The quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued. |
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Per-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job. |
| artifacts | array | – | – |
| capability_id | string | – | – |
| job_id | string | yes | – |
| quote | object | – | – |
| state | – | yes | – |
| verification | object | – | Independent verification. verification.ok = false means the job failed, not a partial success. |
No examples provided.
submit_x402_endpoint_preflight x402 endpoint preflight ~252
Preflight an x402 resource manifest: URL, price, receiving address and its EIP-55 checksum, asset, network and authorization window. Before calling or listing an x402 endpoint, to catch a misconfigured requirement. Do not choose this when you need the live 402 challenge fetched, which needs a request. Example requests: Preflight this x402 endpoint before I call it. | Is this x402 payment requirement safe to pay? | Check my endpoint's payTo address and price. | Will a stock x402 client be able to buy from this endpoint?
| Name | Type | Req | Description |
|---|---|---|---|
| accepted_price | string|number | – | The amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optiona… |
| authorized_by | string | yes | Identifier of the human or agent authorizing this job. |
| inputs | object | yes | – |
| quote_id | string | – | The quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued. |
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Per-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job. |
| artifacts | array | – | – |
| capability_id | string | – | – |
| job_id | string | yes | – |
| quote | object | – | – |
| state | – | yes | – |
| verification | object | – | Independent verification. verification.ok = false means the job failed, not a partial success. |
No examples provided.
submit_xml_json_conversion XML to JSON conversion module with pytest tests ~272
Produce a standard-library Python module that converts an XML document into JSON, plus pytest tests. Choose this when you need a tested, standard-library XML-to-JSON conversion that keeps attributes as '@name' keys and collects repeated elements. Do not choose this when the document uses DTDs, external entities, or namespaces: those are not resolved. It is also a code deliverable, not a conversion of your specific file. Example requests: Write a Python module that converts an XML document into JSON, with tests. | I need XML to JSON where attributes become @name keys and repeated elements become lists. | Generate an XML-to-JSON converter and test it, including malformed XML.
| Name | Type | Req | Description |
|---|---|---|---|
| accepted_price | string|number | – | The amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optiona… |
| authorized_by | string | yes | Identifier of the human or agent authorizing this job. |
| inputs | object | yes | – |
| quote_id | string | – | The quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued. |
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Per-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job. |
| artifacts | array | – | – |
| capability_id | string | – | – |
| job_id | string | yes | – |
| quote | object | – | – |
| state | – | yes | – |
| verification | object | – | Independent verification. verification.ok = false means the job failed, not a partial success. |
No examples provided.
How do I install the SwishrJobs MCP server?
SwishrJobs is a hosted endpoint at https://swishrjobs.com/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 · swishrjobs.com
claude mcp add --transport http com-swishrjobs-swishrjobs 'https://swishrjobs.com/mcp'
What is the SwishrJobs MCP server?
SwishrJobs is an MCP server listed in the public MCP registry as com.swishrjobs/swishrjobs. Deterministic digital jobs with independently verified deliverables. This page covers its hosted endpoint (https://swishrjobs.com/mcp).
Is the SwishrJobs MCP server safe to use?
SwishrJobs scores 60 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 SwishrJobs MCP server expose?
SwishrJobs exposes 114 tools: list_capabilities, get_performance, select_capability, preflight_job, submit_job, and 109 more. Their descriptions and schemas cost roughly 27,462 tokens of context every time the server is loaded.
Does the SwishrJobs MCP server require authentication?
No. We connected to SwishrJobs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SwishrJobs MCP server still maintained?
SwishrJobs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the SwishrJobs MCP server?
VerifyMCP ran 12 checks on SwishrJobs, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SwishrJobs: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.