Home / MCP registry index / com.swishrjobs/swishrjobs

SwishrJobs

com.swishrjobs/swishrjobs in the official MCP registry. Endpoint https://swishrjobs.com/mcp. Source: github.com/Mahmoudaly187/swishrjobs.

The registry describes it as: Deterministic digital jobs with independently verified deliverables.

We read its 114 tools on 2026-11-04. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http swishrjobs https://swishrjobs.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "swishrjobs": {
      "url": "https://swishrjobs.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"swishrjobs","type":"http","url":"https://swishrjobs.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_capabilities get_performance select_capability preflight_job submit_job submit_a2a_card_validator submit_accessibility_conformance_audit submit_agent_cost_attribution submit_agent_trace_analyser submit_api_contract_diff submit_backtest_overfitting_check submit_bank_statement_reconciler submit_boundary_value_generation submit_cli_tool_scaffold submit_commerce_conformance_suite submit_compliance_evidence_pack submit_compliance_readiness_pack submit_cron_expression_check submit_csv_clean submit_csv_column_profile submit_csv_date_normalise submit_csv_deduplicate submit_csv_dialect_report submit_csv_json_transformation submit_csv_missing_value_report submit_csv_preflight submit_csv_quality_report submit_csv_to_json_rows submit_dashboard_spec_from_questions submit_data_lineage_graph submit_data_migration_readiness_pack submit_data_validation_module submit_database_migration_review submit_dataset_quality_report submit_dbt_test_generation submit_dependency_vulnerability_triage submit_dq_rules_generator submit_duplicate_group_report submit_edge_case_check submit_embedding_similarity_report submit_env_config_parsing submit_env_file_check submit_eval_dataset_builder submit_expense_policy_checker submit_feature_flag_audit submit_field_mapping submit_financial_ratio_report submit_fine_tune_data_formatter submit_fx_rate_normaliser submit_guardrail_policy_config submit_html_text_extraction submit_iban_bic_validator submit_invoice_data_extraction submit_iso20022_validator submit_json_csv_conversion submit_json_diff submit_json_key_audit submit_json_ndjson_check submit_json_schema_inference submit_json_schema_validation and 54 more

Tool changes

This server changed its tools after we first read them. If you approved it before the latest change, what you approved is not what it serves now: read its tools again.

Between 2026-11-03 and 2026-11-04 it added submit_a2a_card_validator, submit_accessibility_conformance_audit, submit_agent_cost_attribution, submit_agent_trace_analyser, submit_api_contract_diff, submit_backtest_overfitting_check, submit_bank_statement_reconciler, submit_cli_tool_scaffold and 67 more; changed what these tools say: preflight_job, submit_job, submit_unit_conversion_library.
Between 2026-11-02 and 2026-11-02 it added submit_unit_conversion_library; changed what these tools say: preflight_job, submit_job.
Between 2026-10-31 and 2026-11-02 it added submit_json_to_csv_rows; changed what these tools say: preflight_job, submit_job.

Fingerprint of its tools at our last full read (2026-11-04): 2939ea96a49e6652. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-swishrjobs-swishrjobs/badge.svg)](https://lazaretto.dev/mcp-registry/com-swishrjobs-swishrjobs)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.