Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Nock

REMOTE · API.USENOCK.COM

Brazilian B2B prospecting: buying signals, company and people search, enrichment and outreach.

Available components

+3 this week 76 Trust /100

Last scanned (22 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security89
Transport & Reachability100
Schema Quality & AI Usability53
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 35542 tokens (~332/item across 107 items; 107 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 Management26
  • Stability check failed: schema churn in the 8 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 8 additions. See how to fix → Fail
Tool Coverage92
  • 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 108 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 21 Nov 26 0
    • New tool “update_campaign_audience”, which the server declares destructive security
    • Tool “update_campaign_settings” rewrote its description, which is the text the model reads security
    • “update_campaign_settings” added an optional parameter “manualLinkedin” cosmetic
    • “update_knowledge_base” added an optional parameter “emailFooter” cosmetic
  • 20 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_whatsapp” rewrote its description, which is the text the model reads security
    • Tool “create_signal_monitor” rewrote its description, which is the text the model reads security
    • Tool “explore_signals” rewrote its description, which is the text the model reads security
    • Tool “find_companies_using_erp” rewrote its description, which is the text the model reads security
    • Tool “find_companies_with_signal” rewrote its description, which is the text the model reads security
    • Tool “get_sheet_rows” rewrote its description, which is the text the model reads security
    • Tool “select_sheet_rows” rewrote its description, which is the text the model reads security
    • Tool “update_campaign_settings” rewrote its description, which is the text the model reads security
    • Tool “update_outreach_cadence” rewrote its description, which is the text the model reads security
    • Tool “update_signal_monitor” rewrote its description, which is the text the model reads security
    • New tool “check_sheet_signals” functional
    • “explore_signals” added an optional parameter “confirmed” cosmetic
    • “find_companies_using_erp” added an optional parameter “companies” cosmetic
    • “find_companies_using_erp” added an optional parameter “companiesSheetId” cosmetic
    • “find_companies_using_erp” added an optional parameter “decisionMakerFallback” cosmetic
    • “find_companies_using_erp” added an optional parameter “includeWeakProof” cosmetic
    • “find_companies_with_signal” added an optional parameter “decisionMakerFallback” cosmetic
    • “generate_outreach_campaign” added an optional parameter “withSignalOnly” cosmetic
    • “get_sheet_rows” added an optional parameter “filters” cosmetic
    • “get_sheet_rows” added an optional parameter “search” cosmetic
    • “select_sheet_rows” added an optional parameter “filters” cosmetic
    • “select_sheet_rows” added an optional parameter “search” cosmetic
    • “update_campaign_settings” added an optional parameter “extraWhatsappAccountIds” cosmetic
    • “update_campaign_settings” added an optional parameter “whatsappDistribution” cosmetic
    • “update_campaign_settings” added an optional parameter “whatsappMode” cosmetic
    • “update_campaign_settings” added an optional parameter “whatsappRoundRobinMembers” cosmetic
    • “create_outreach_campaign” reworded the description of “cadence” cosmetic
    • “find_companies_using_erp” reworded the description of “area” cosmetic
    • “find_companies_using_erp” reworded the description of “hiringArea” cosmetic
    • “find_companies_using_erp” reworded the description of “jobPostTitles” cosmetic
    • “find_companies_using_erp” reworded the description of “jobTitle” cosmetic
    • “find_companies_using_erp” reworded the description of “limit” cosmetic
    • “find_companies_with_signal” reworded the description of “limit” cosmetic
    • “select_sheet_rows” made “rowIds” optional cosmetic
  • 19 Nov 26 0
    • Stability: 0.17 → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “add_prospects_to_campaign” rewrote its description, which is the text the model reads security
    • Tool “add_rows_to_sheet” rewrote its description, which is the text the model reads security
    • Tool “create_sheet” rewrote its description, which is the text the model reads security
    • Tool “create_signal_monitor” rewrote its description, which is the text the model reads security
    • Tool “discover_decision_makers” rewrote its description, which is the text the model reads security
    • Tool “explore_signals” rewrote its description, which is the text the model reads security
    • Tool “export_sheet_csv” rewrote its description, which is the text the model reads security
    • Tool “feed_campaign_with_signal” rewrote its description, which is the text the model reads security
    • Tool “find_companies_with_rules” rewrote its description, which is the text the model reads security
    • Tool “generate_outreach_campaign” rewrote its description, which is the text the model reads security
    • Tool “get_sheet_rows” rewrote its description, which is the text the model reads security
    • Tool “install_site_tracker” rewrote its description, which is the text the model reads security
    • Tool “list_enrichment_fields” rewrote its description, which is the text the model reads security
    • Tool “list_sheets” rewrote its description, which is the text the model reads security
    • Tool “qualify_sheet_leads” rewrote its description, which is the text the model reads security
    • Tool “restore_company_sheet” rewrote its description, which is the text the model reads security
    • Tool “run_sheet_enrichment” rewrote its description, which is the text the model reads security
    • Tool “set_campaign_signal_monitor” rewrote its description, which is the text the model reads security
    • Schema quality: 276 → 307 ▼ functional
    • “generate_outreach_campaign” made “sheetId” required, so existing callers break ▼ functional
    • New tool “find_companies_using_erp” functional
    • New tool “find_companies_with_signal” functional
    • “export_sheet_csv” added an optional parameter “perCompany” cosmetic
    • “feed_campaign_with_signal” added an optional parameter “confirmed” cosmetic
    • “feed_campaign_with_signal” added an optional parameter “runBeforeActive” cosmetic
    • “set_campaign_signal_monitor” added an optional parameter “runBeforeActive” cosmetic
    • “generate_outreach_campaign” reworded the description of “sheetId” cosmetic
    • “run_sheet_enrichment” reworded the description of “columnId” cosmetic
    • Tool “generate_outreach_campaign” changed its title: Criar campanha com um clique → Criar campanha a partir de planilha cosmetic
  • 18 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “update_campaign_signals”, which the server declares destructive security
    • Tool “activate_outreach_campaign” rewrote its description, which is the text the model reads security
    • Tool “create_signal_monitor” rewrote its description, which is the text the model reads security
    • Tool “explore_signals” rewrote its description, which is the text the model reads security
    • Tool “generate_outreach_campaign” rewrote its description, which is the text the model reads security
    • Tool “get_prospect” rewrote its description, which is the text the model reads security
    • Tool “list_enrichment_fields” rewrote its description, which is the text the model reads security
    • Tool “list_prospects” rewrote its description, which is the text the model reads security
    • Tool “set_autonomy_level” rewrote its description, which is the text the model reads security
    • Tool “set_campaign_signal_monitor” rewrote its description, which is the text the model reads security
    • New tool “assign_prospects” functional
    • “add_enrichment_to_sheet” added an optional parameter “employeeRole” cosmetic
    • “search_people” added an optional parameter “companyRevenueMax” cosmetic
    • “search_people” added an optional parameter “companyRevenueMin” cosmetic
    • “set_autonomy_level” added an optional parameter “confirmed” cosmetic
    • “set_campaign_signal_monitor” added an optional parameter “add” cosmetic
    • “set_campaign_signal_monitor” added an optional parameter “confirmed” cosmetic
    • “set_campaign_signal_monitor” added an optional parameter “replaces” cosmetic
    • “update_campaign_settings” added an optional parameter “skipNationalHolidays” cosmetic
    • “generate_outreach_campaign” reworded the description of “channels” cosmetic
    • “search_companies” reworded the description of “city” cosmetic
    • “search_companies” reworded the description of “revenueMax” cosmetic
    • “search_companies” reworded the description of “revenueMin” cosmetic
    • “search_companies” reworded the description of “useBrazilianRegistryFilters” cosmetic
  • 17 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “activate_outreach_campaign” rewrote its description, which is the text the model reads security
    • Tool “add_prospects_to_campaign” rewrote its description, which is the text the model reads security
    • Tool “create_outreach_campaign” rewrote its description, which is the text the model reads security
    • Tool “create_signal_monitor” rewrote its description, which is the text the model reads security
    • Tool “explore_signals” rewrote its description, which is the text the model reads security
    • Tool “generate_outreach_campaign” rewrote its description, which is the text the model reads security
    • Tool “update_campaign_settings” rewrote its description, which is the text the model reads security
    • Tool “update_signal_monitor” rewrote its description, which is the text the model reads security
    • “update_campaign_settings” added an optional parameter “onlyActiveLinkedin” cosmetic
    • “update_prospect” added an optional parameter “name” cosmetic
  • 15 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “feed_campaign_with_signal” rewrote its description, which is the text the model reads security
    • Tool “run_sheet_enrichment” rewrote its description, which is the text the model reads security
    • Tool “update_campaign_settings” rewrote its description, which is the text the model reads security
    • New tool “install_site_tracker” functional
    • New tool “list_site_visitors” functional
    • “run_sheet_enrichment” added an optional parameter “columnIds” cosmetic
    • “run_sheet_enrichment” added an optional parameter “confirmed” cosmetic
    • “run_sheet_enrichment” added an optional parameter “force” cosmetic
    • “run_sheet_enrichment” reworded the description of “columnId” cosmetic
    • “search_companies” reworded the description of “companyOrder” cosmetic
    • “update_campaign_settings” reworded the description of “blockActiveSequence” cosmetic
    • “update_campaign_settings” reworded the description of “blockContactedBefore” cosmetic
    • “run_sheet_enrichment” made “columnId” optional cosmetic
  • 14 Nov 26 +3

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • Injection markers: fail → pass ▲ security
    • Tool “accept_received_invitation” rewrote its description, which is the text the model reads security
    • Tool “activate_outreach_campaign” rewrote its description, which is the text the model reads security
    • Tool “add_cadence_rule” rewrote its description, which is the text the model reads security
    • Tool “add_enrichment_to_sheet” rewrote its description, which is the text the model reads security
    • Tool “add_prospects_to_campaign” rewrote its description, which is the text the model reads security
    • Tool “add_rows_to_sheet” rewrote its description, which is the text the model reads security
    • Tool “adjust_outreach_cadence” rewrote its description, which is the text the model reads security
    • Tool “ai_column” rewrote its description, which is the text the model reads security
    • Tool “approve_inbox_message” rewrote its description, which is the text the model reads security
    • Tool “brain_lookup” rewrote its description, which is the text the model reads security
    • Tool “brief_lead” rewrote its description, which is the text the model reads security
    • Tool “company_group” rewrote its description, which is the text the model reads security
    • Tool “company_products” rewrote its description, which is the text the model reads security
    • Tool “confirm_decision_maker” rewrote its description, which is the text the model reads security
    • Tool “create_outreach_campaign” rewrote its description, which is the text the model reads security
    • Tool “create_routine” rewrote its description, which is the text the model reads security
    • Tool “create_sheet” rewrote its description, which is the text the model reads security
    • Tool “create_signal_monitor” rewrote its description, which is the text the model reads security
    • Tool “delete_prospect” rewrote its description, which is the text the model reads security
    • Tool “delete_routine” rewrote its description, which is the text the model reads security
    • Tool “delete_sheet” rewrote its description, which is the text the model reads security
    • Tool “discover_decision_makers” rewrote its description, which is the text the model reads security
    • Tool “disqualify_prospect” rewrote its description, which is the text the model reads security
    • Tool “edit_sheet” rewrote its description, which is the text the model reads security
    • Tool “enrich_field” rewrote its description, which is the text the model reads security
    • Tool “enrich_field_batch” rewrote its description, which is the text the model reads security
    • Tool “explore_signals” rewrote its description, which is the text the model reads security
    • Tool “export_signal_events” rewrote its description, which is the text the model reads security
    • Tool “feed_campaign_with_signal” rewrote its description, which is the text the model reads security
    • Tool “find_companies_with_rules” rewrote its description, which is the text the model reads security
    • Tool “find_lead” rewrote its description, which is the text the model reads security
    • Tool “find_people_for_campaign” rewrote its description, which is the text the model reads security
    • Tool “forget_memory” rewrote its description, which is the text the model reads security
    • Tool “generate_outreach_campaign” rewrote its description, which is the text the model reads security
    • Tool “get_credit_balance” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • “ai_column” added an optional parameter “web” cosmetic
    • “activate_outreach_campaign” reworded the description of “campaignId” cosmetic
    • “activate_outreach_campaign” reworded the description of “linkedinAccountId” cosmetic
    • “activate_outreach_campaign” reworded the description of “mailboxId” cosmetic
    • “activate_outreach_campaign” reworded the description of “whatsappAccountId” cosmetic
    • “activate_prospect_channel” reworded the description of “prospectId” cosmetic
    • “add_prospects_to_campaign” reworded the description of “campaignId” cosmetic
    • “add_prospects_to_campaign” reworded the description of “includeRemoved” cosmetic
    • “add_prospects_to_campaign” reworded the description of “sheetId” cosmetic
    • “add_rows_to_sheet” reworded the description of “rows” cosmetic
    • “add_rows_to_sheet” reworded the description of “sheetId” cosmetic
    • “adjust_outreach_cadence” reworded the description of “campaignId” cosmetic
    • “approve_inbox_message” reworded the description of “prospectId” cosmetic
    • “brief_lead” reworded the description of “refresh” cosmetic
    • “confirm_decision_maker” reworded the description of “person” cosmetic
    • “create_outreach_campaign” reworded the description of “cadence” cosmetic
    • “create_outreach_campaign” reworded the description of “goal” cosmetic
    • “create_outreach_campaign” reworded the description of “linkedinAccountId” cosmetic
    • “create_outreach_campaign” reworded the description of “mailboxId” cosmetic
    • “create_outreach_campaign” reworded the description of “rowIds” cosmetic
    • “create_outreach_campaign” reworded the description of “sheetId” cosmetic
    • “create_outreach_campaign” reworded the description of “templateId” cosmetic
    • “create_outreach_campaign” reworded the description of “whatsappAccountId” cosmetic
    • “create_routine” reworded the description of “campaignId” cosmetic
    • “create_routine” reworded the description of “columnId” cosmetic
    • “create_routine” reworded the description of “sheetId” cosmetic
    • “delete_outreach_template” reworded the description of “templateId” cosmetic
    • “delete_prospect” reworded the description of “prospectId” cosmetic
    • “delete_routine” reworded the description of “routineId” cosmetic
    • “disqualify_prospect” reworded the description of “prospectId” cosmetic
    • “enrich_field” reworded the description of “fieldId” cosmetic
    • “enrich_field” reworded the description of “refresh” cosmetic
    • “enrich_field_batch” reworded the description of “fieldId” cosmetic
    • “enrich_field_batch” reworded the description of “people” cosmetic
    • “enrich_field_batch” reworded the description of “refresh” cosmetic
    • “find_people_for_campaign” reworded the description of “campaignId” cosmetic
    • “generate_outreach_campaign” reworded the description of “sheetId” cosmetic
    • “get_inbox_conversation” reworded the description of “prospectId” cosmetic
    • “get_prospect” reworded the description of “prospectId” cosmetic
  • 13 Nov 26 +34

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

Diagnostics

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 21 Nov 2026 · Probed https://api.usenock.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.usenock.com CN=WR3,O=Google Trust Services,C=US 1 Nov 2026 30 Jan 2027 RSA 2048 SHA256-RSA 2c74e8b3a8e81d0d120b7d99a2ba771f
SANs: api.usenock.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.usenock.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
usenock.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://api.usenock.com/.well-known/oauth-protected-resource/mcp", scope="openid profile email"

Bearer resource_metadata="https://api.usenock.com/.well-known/oauth-protected-resource/mcp", scope="openid profile email"

Protected resource metadata

Document https://api.usenock.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://api.usenock.com/mcp
Authorisation server https://clerk.usenock.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.usenock.com/mcp Verified 200
http (plaintext) http://api.usenock.com/mcp HTTPS enforced
MCP tools · 107 exposed · ~32,897 tokens

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 →

Tool Tokens
update_customer_list ~73

Change the workspace's customer list. mode add puts companies on it, remove takes them off, replace swaps the whole list (only when the user sends their full list). lines: one company name or site per line, or "Name, site".

NameTypeReqDescription
linesstringyes–
modestringyes–

No output schema declared.

No examples provided.

update_knowledge_base ~248

Change the workspace's company profile. Only the fields sent change; send the full new text of a section you rewrite. Campaigns written afterwards use it.

NameTypeReqDescription
cadenceRulesstring–The full new text of the cadence rules, one rule per line, to edit or remove one. Adding a single rule has its own tool.
competitorsstring–Competitors.
contextstring–What the company is and does.
emailFooterstring–The account's e-mail footer, the whole text ("" clears it): the company's address and how to stop receiving. Added after the signature of every cadence e-mail at send, always the same words; never wr…
exclusionsstring–Who never to prospect.
featuresstring–What the product does, one capability per item ("a; b; c").
idealCustomerProfilestring–Ideal customer profile.
namestring––
offeringstring–What it sells.
painPointsstring–Problems it solves.
personastring–Who buys: roles and their day.
websitestring––

No output schema declared.

No examples provided.

update_outreach_cadence ~632

Changes the cadence of ONE campaign: the shared template every person gets, and people added later. A change of form or tone (lowercase, more formal, shorter, another greeting, no emoji) applies to every step. A change of content or structure (add a question, mention something, change the argument) applies to the step it points to (a day, a channel, a sentence only that step has), not to every step, unless it is about every message. Each follow-up keeps its own new reason to reply (a case, how the work is done, a resource, what changes for the reader), and the last step keeps closing the subject. requestedDays lists the steps the request covers; edits on any other day are refused (a new step, op add, always fits). To change one or a few steps, pass `edits` (day or "last", optional channel, new body; op add/remove/move to insert, delete or reschedule a step, op condition to change what lets a step go: no reply in N days, the invite accepted, or the e-mail before it opened) and the other steps stay as they are; `steps` replaces the whole cadence. A step may carry `variantB` (a version B for an A/B test, subject for e-mail only): it is saved with the exact text given, never rewritten, in the same place as a version B made on the cadence screen; an edit with only variantB leaves version A as it is, and variantB null removes it. A LinkedIn connection request and a like step take no version B (the result lists them in versionBNotSaved). With both, edits win and steps is ignored; a call that carries every text twice can be cut off. scope is "template" (the default) for any wording change, including 'the template', 'every day' or 'everyone', even while the screen shows one example person; "one_person" with prospectId changes only that one person's messages. A prospectId without scope "one_person" is ignored. Does not activate sending. A template change saves the template only: the people's steps not sent yet take it with its fields to write, and nobody is written again unt…

NameTypeReqDescription
campaignIdstringyesExact campaign UUID.
editsarray–Steps to change; every other step is kept.
prospectIdstring–Prospect UUID, read only with scope one_person.
requestedDays––The days of the steps the request asks to change (the step open on the user's screen when the request does not say), or "all" for a change of form or tone or a change to every message. Edits on any o…
scopestring–template (default): the shared template and everyone on it. one_person: only prospectId's messages.
stepsarray–Full replacement cadence in send order. Use edits instead to change a few steps.

No output schema declared.

No examples provided.

update_outreach_campaign ~650

Edits the settings of ONE outreach campaign the user owns, by campaignId. Only the fields passed change; the others keep their value. Fields: campaign name, offering (what the user's company sells), give (something useful offered before asking for the reader's time, such as a diagnosis, a sample or a draft), sender name, company, role and URL, tone, goal, call to action, message length, constraints (what the messages must never say), business context, and which connected Gmail mailbox, LinkedIn or WhatsApp account sends. It sends no message, adds or removes no people, does not start, pause or resume the campaign, and does not edit the cadence's messages. "O que a campanha oferece" (the activation item) and "O que você dá antes de pedir" are the give, not the offering. A new give on a campaign that already has a cadence writes the cadence's template again from it right away; the people's messages are not rewritten by this call: the result's messagesOutdated counts them and messagesNext describes the rewrite still pending.

NameTypeReqDescription
businessContextstring–Company and product context the campaign's messages respect. Leave it out to keep it.
campaignIdstringyesExact campaign UUID.
constraintsstring–Things the copy must never say or do. Leave it out to keep it.
ctastring–Desired next step: reply, book_call, accept_connect, share_resource, or custom text.
givestring–"O que a campanha oferece": concrete value handed over before asking for the reader's time (a diagnosis, a sample, a draft). Leave it out to keep it.
goalstring–Campaign objective: conversion, awareness, consultative, meeting, relationship, or custom text.
linkedinAccountIdstring–Connected LinkedIn accountId. Leave it out to keep it.
mailboxIdstring–Connected Gmail mailbox UUID. Leave it out to keep it.
messageLengthstring––
namestring–New campaign name.
offeringstring–What the company sells / the offer used in generated messages.
rewriteMessagesboolean–A new give writes the cadence's template again by default; false only when the user asked to keep the messages as they are.
senderCompanystring–Sender company name. Leave it out to keep it.
senderCompanyUrlstring–Sender company URL. Leave it out to keep it.
senderLinkChannelsarray–Channels that may include the sender link: email, linkedin, whatsapp.
senderNamestring–Name used in message signatures. Leave it out to keep it.
senderRolestring–Sender role. Leave it out to keep it.
signalGatestring–How to use company buying signals: personalize messages, or skip people missing the chosen signal.
tonestring–Message tone, e.g. consultative, professional, friendly, direct.
whatsappAccountIdstring–Connected WhatsApp accountId. Leave it out to keep it.

No output schema declared.

No examples provided.

update_outreach_campaign_status ~132

Pause or resume ONE campaign cadence, or archive it. Pausing prevents new sends and freezes the schedule. Resuming may send the next due step immediately when inside the business window. "archived" keeps the people, the sends, the replies and the reports, stops everything and takes it out of the campaign list; "paused" on an archived campaign unarchives it (paused, or a draft when it never ran). Archiving is the way to put away a campaign: deleting erases its send history.

NameTypeReqDescription
campaignIdstringyesExact campaign UUID.
statusstringyes–

No output schema declared.

No examples provided.

update_prospect ~166

Update ONE prospect owned by the authenticated user: move it through the pipeline and/or rewrite its message. Editing a message never regenerates it and never costs credits. Statuses: ready, sending, awaiting_reply, replied, paused, failed. Setting awaiting_reply stamps the sent time; replied stamps the reply time.

NameTypeReqDescription
connectionNotestring–Replacement LinkedIn connection note (300 characters max).
emailBodystring––
emailSubjectstring––
namestring–The person's real name, fixed by hand (not the company's name, an e-mail or a guess). A person held "sem nome" goes back in line once the name is valid.
prospectIdstringyesExact prospect UUID.
statusstring––

No output schema declared.

No examples provided.

update_signal_monitor ~164

Change a signal monitor: its filters, name, schedule, monthly credit limit, destination sheet, or pause/resume it. Only the fields sent change. A market monitor also takes dailyLimit, market (its whole filter set, same signal) and contact (who to bring at each company; on a cnpj monitor a role such as "Gerente de loja", +8 credits only when found, and null goes back to the Receita's sócio-administrador, free). An engagement signal takes addPeople and removePeople (LinkedIn profile URLs; a founder found on its own can be removed too; at most 30 named profiles); its watchedProfiles say whose posts it reads.

NameTypeReqDescription
monitorIdstringyesSignal monitor id.
patch–yes–

No output schema declared.

No examples provided.

Install

How do I install the Nock MCP server?

Nock is a hosted endpoint at https://api.usenock.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 · api.usenock.com

# add to Claude Code
claude mcp add --transport http com-usenock-nock 'https://api.usenock.com/mcp'
Common questions

What is the Nock MCP server?

Nock is an MCP server listed in the public MCP registry as com.usenock/nock. Brazilian B2B prospecting: buying signals, company and people search, enrichment and outreach. This page covers its hosted endpoint (https://api.usenock.com/mcp).

Is the Nock MCP server safe to use?

Nock scores 76 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 Nock MCP server expose?

Nock exposes 107 tools: create_sheet, list_sheets, get_sheet_rows, qualify_sheet_leads, add_rows_to_sheet, and 102 more. Their descriptions and schemas cost roughly 32,897 tokens of context every time the server is loaded.

Does the Nock MCP server require authentication?

Yes. Nock asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Nock MCP server still maintained?

Nock is still listed as active in the MCP registry. We last reached this channel on 21 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 Nock MCP server?

VerifyMCP ran 13 checks on Nock, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.