Home / MCP registry index / com.usenock/nock

Nock

com.usenock/nock in the official MCP registry. Endpoint https://api.usenock.com/mcp. Source: github.com/nock-ltda/nock-mcp.

The registry describes it as: Brazilian B2B prospecting: buying signals, company and people search, enrichment and outreach.

Connect it

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

claude mcp add --transport http nock https://api.usenock.com/mcp

{
  "mcpServers": {
    "nock": {
      "url": "https://api.usenock.com/mcp"
    }
  }
}

code --add-mcp '{"name":"nock","type":"http","url":"https://api.usenock.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.

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

create_sheet list_sheets get_sheet_rows qualify_sheet_leads add_rows_to_sheet add_enrichment_to_sheet discover_decision_makers identify_business confirm_decision_maker check_whatsapp find_companies_with_rules company_group company_products feed_campaign_with_signal import_linkedin_connections phone_owner clean_phone edit_sheet select_sheet_rows export_sheet_csv run_sheet_enrichment run_sheet_ai_column search_people search_companies list_enrichment_fields enrich_field enrich_field_batch research_web send_to_webhook ai_column list_outreach_templates save_outreach_template delete_outreach_template list_outreach_campaigns list_outreach_senders create_outreach_campaign generate_outreach_campaign update_outreach_campaign set_campaign_daily_people find_people_for_campaign set_campaign_signal_monitor update_outreach_cadence regenerate_outreach_cadence adjust_outreach_cadence update_cadence_ai_field list_cadence_versions restore_cadence_version preview_campaign_messages rewrite_campaign_messages add_prospects_to_campaign activate_outreach_campaign update_outreach_campaign_status list_prospects get_prospect update_prospect delete_prospect disqualify_prospect set_prospect_closure_reason activate_prospect_channel send_prospect_step_now and 39 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-12): 051c2df2f2f99ed3. 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:

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

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.