Nock
REMOTE · API.USENOCK.COM
Brazilian B2B prospecting: buying signals, company and people search, enrichment and outreach.
Available components
Last scanned (21 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
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 →
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.
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 |
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_sheet_rows Ler linhas da planilha ~285
Reads rows from ONE sheet the user owns. Returns each exact row id plus non-empty cell values with their visible column labels and stable column ids. Reads up to 25 rows at a time with offset/limit, or known rowIds directly; filters and search read only the rows that pass them, as the sheet's Filtrar and Buscar do (matchingRows says how many). For a people sheet, contactColumns lists LinkedIn, E-mail and Telefone as the app shows them, each with the column that holds it and the column id that reveals it. Read-only and free. Each row comes with kind ("person", or "company" for a company without a person yet) and company (its id, name, domain and CNPJ, the same for every person of that company).
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | Only the rows that pass every filter, as the sheet's Filtrar does. |
| limit | integer | – | Rows to return when rowIds is omitted. Defaults to 25. |
| offset | integer | – | Zero-based row offset when rowIds is omitted. Defaults to 0. |
| rowIds | array | – | Optionally read only these exact row ids, preserving this order. |
| search | string | – | Only the rows whose name, company, role or e-mail hold this text. |
| sheetId | string | yes | Exact sheet UUID. |
No output schema declared.
No examples provided.
identify_business Identificar decisor de pequena empresa ~453
Find who decides in a SMALL business (a school, a market, a clinic) and how to reach them: name, role, the public origin of each fact (company site, Google Maps, Receita Federal, Instagram…), a work e-mail, the owner's mobile when it can be confirmed. Takes a name and city (and state), or a CNPJ, or a website. Charged only for what is found: 8 credits for a decision maker our search found (site, Maps, web, gazette, LinkedIn), free when the only source is the Receita's list of partners; 8 for the person's e-mail, 15 for the owner's mobile; nothing when nothing is found. A business already in our base answers at once at the same price. One business per call; a list takes one call per row. With prospectId (or sheetId and rowId) of a person of a campaign or a sheet row, the decision makers with evidence and the numbers, with whose they are, are saved to that person (the mobile goes to their phone only when it is theirs); savedTo says where. Each result names the business it is about, so parallel calls are told apart by business, not by order.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| cnpj | string | – | – |
| inepCode | string | – | The customer's own key for the row; never searched. |
| maxCredits | integer | – | A cap on what this business may cost, in credits. |
| name | string | – | The business's name as the customer knows it. |
| phone | string | – | The business's own phone from the customer's list; checked first. |
| prospectId | string | – | The campaign prospect this business is looked up for: what is found with evidence is saved to them. |
| rowId | string | – | The sheet row this business is looked up for, with sheetId. |
| sheetId | string | – | The sheet of the row this business is looked up for, with rowId. |
| state | string | – | Two-letter state, e.g. SP. |
| want | array | – | What to look for; default everything. |
| website | string | – | – |
No output schema declared.
No examples provided.
import_linkedin_connections Importar conexões do LinkedIn ~274
Warm campaign source: reads the user's own LinkedIn first-degree connections (free, from the LinkedIn account the user connected to Nock; never anyone else's network) into a new people sheet in the user's workspace, newest first, keeping those whose headline has any of the keywords (their ICP's titles or sectors). Only the professional profile LinkedIn shows a connection (name, headline, profile URL), at most 1000 per call. For a campaign with people who already know the user (their connections, their network). It says itself when no LinkedIn is connected or which account to pick, so no sender check is needed before it. Returns how many were read and kept, a sample and the sheet. A message to someone already connected needs no invite and gets more replies. LinkedIn does not share who viewed the profile through this account, so that is not available.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | – | The LinkedIn account when the workspace has more than one. |
| keywords | array | – | Words to keep connections whose headline has any of them (titles, sectors, companies): e.g. ["CEO", "fundador", "diretor comercial", "varejo"]. Empty keeps all. |
| max | integer | – | How many recent connections to read (default 500, at most 1000). |
No output schema declared.
No examples provided.
install_site_tracker Instalar o rastreador do site ~287
Creates or changes the workspace's website tracker (the 'Visitou seu site' signal) and returns the install snippet: two script lines the customer puts before </head> on every page of their site, the domains it accepts visits from (the workspace's site by default), and a default paragraph for their privacy policy. The script identifies the COMPANY behind a visit by its network (not the person); a person only when they identify themselves: tagCampaignLinks adds a signed nk parameter to the campaign links that point to the customer's own site, and a form can call nock.identify(email). consentMode 'notice' respects Do Not Track; 'opt_in' sends nothing before nock.consent(true). citeVisits lets messages mention the visit (off by default: the visit only times the message). Visits are kept 90 days. Free. Once installed, the visiting companies can feed a signal monitor of category 'visitor' (periodDays 7/14/30, minStrength 0-100, buyingPagesOnly; 2 credits per company, +8 per decision maker our search found).
| Name | Type | Req | Description |
|---|---|---|---|
| citeVisits | boolean | – | – |
| consentMode | string | – | – |
| domains | array | – | The site's domains, e.g. ["acme.com.br"]; subdomains are included. |
| status | string | – | – |
| tagCampaignLinks | boolean | – | – |
No output schema declared.
No examples provided.
list_cadence_versions Versões da cadência ~74
List the earlier versions of a campaign's cadence template, newest first: when each was replaced and the start of each step. Every change to the template keeps the version it replaced (up to 30). For getting an earlier version back or seeing what changed.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | Exact campaign UUID. |
No output schema declared.
No examples provided.
list_enrichment_fields Campos de enriquecimento ~208
Lists the enrichment fields currently available in Nock, with the same catalogue, configured-provider filtering, input definitions, provider order and credit prices shown in the dashboard's Tools drawer. Each field id and its inputs are what a single-field enrichment takes. creditCost is the most per row found; a field with creditCostLabel has a price that depends on the source ("WhatsApp do decisor da empresa": 6 a 15 créditos por número achado, 6 for a number the business publishes, 15 for the partner's own mobile): quote that label and use creditCost for the maximum. Read-only and free. Every field fits any sheet. scope says how it runs: "person" once per person (companies without a person are skipped), "company" once per company, charged once and shown on every person of it.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| mode | string | – | – |
| query | string | – | Optional text filter over field names and descriptions. |
No output schema declared.
No examples provided.
list_inbox_conversations Listar conversas da caixa de entrada ~90
List the Inbox conversations with campaign people, newest first: who replied, the last message preview and any step waiting for approval (pendingApproval). Optional filters narrow to replies, pending approvals or one campaign.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | – | – |
| onlyPendingApproval | boolean | – | Only conversations with a step waiting for approval. |
| onlyReplies | boolean | – | Only conversations where the person replied. |
No output schema declared.
No examples provided.
list_outreach_campaigns Listar campanhas de prospecção ~150
List the authenticated user's prospecting campaigns with their pipeline totals per status, including each campaign's objective (goal) and CTA, so the objectives already running are known. With campaignId it also returns abTests: each cadence step under an A/B test with sends, replies and reply rate per version and the rule that picks the winner. Archived campaigns (status archived: kept with their history, sending nothing) are left out unless archived is "include" or "only"; campaignId finds one either way. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | string | – | Archived campaigns: exclude (default), include or only. |
| campaignId | string | – | Optionally return only this campaign, including its prospects. |
No output schema declared.
No examples provided.
list_outreach_senders Listar contas de envio ~192
List the authenticated user's connected outreach senders: Gmail mailboxes, LinkedIn accounts and WhatsApp accounts, with the exact mailboxId / linkedinAccountId / whatsappAccountId other inputs take. Each LinkedIn account sends at most 30 invites and messages a day, shared by every campaign that sends from it, and each campaign at most its own linkedinDailyLimit (20 by default, a campaign setting); both count LinkedIn only, never the cadence's e-mails. sentToday and sentTodayByCampaign say how much of today's quota is used and by which campaign. When a campaign's account is full, its LinkedIn steps wait for tomorrow; a campaign can be moved to another account of the workspace with room. The account limit is fixed per workspace (30 for most); it cannot be raised here. A channel that is not listed is not connected; it is connected in Settings → Integrations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_outreach_templates Listar templates de prospecção ~65
Lists the authenticated user's saved outreach templates. Each template carries the reusable campaign configuration: offer, sender name, tone, business/company context and language. Read-only. Only templateIds returned here are valid; a campaign can also be created without a template, from name and offering.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_prospects Listar prospecções ~112
Lists the authenticated user's prospects (people with a generated message) with their pipeline status, optionally filtered by campaign or status, and each one's owner ("Responsável": the workspace member who sends the person's WhatsApp tasks, null for nobody). Returns a compact summary, without the full message and history.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | – | Only prospects of this campaign. |
| limit | integer | – | Max prospects to return (default and max 50). |
| status | string | – | Only prospects in this pipeline status. |
No output schema declared.
No examples provided.
list_received_invitations Convites recebidos no LinkedIn ~91
List the LinkedIn connection requests the user's connected account received: who asked to connect, their headline and what they wrote. Someone from the ICP who asked to connect is a warm lead. Read only and free; accepting a request is not done by this tool. If the workspace has several LinkedIn accounts, pass accountId.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_routines Listar rotinas do Nock Agent ~53
List the workspace's routines (what runs, when, the credit cap, active or paused, next run), the autonomy level of each action type, and the last actions the Nock Agent took or suggested. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sheets Listar planilhas ~86
List the authenticated user's enrichment sheets. Returns each exact sheet id, name, people/company mode, row count, and referenceable columns. Read-only. Every sheet takes people and companies; mode is ignored. Each sheet comes with how many people and how many companies without a person it holds (content).
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | Optionally return only people sheets or only company sheets. |
No output schema declared.
No examples provided.
list_signal_events Listar eventos de sinais ~57
Read saved signal events, from one monitor or the whole workspace, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| monitorId | string | – | – |
| query | string | – | Text to find in the company, person or title. |
No output schema declared.
No examples provided.
list_signal_monitors Listar monitoramentos ~29
List the workspace's signal monitors: category, filters, status, schedule and monthly credit limit.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_site_visitors Empresas que visitaram o site ~117
Companies that visited the workspace's website (through the workspace's site tracker), strongest first: pages and sessions, whether they saw prices or a demo, first and last visit, people who identified themselves, and a strength 0-100 (recency, frequency, buying pages). Free. Meant as timing: messages do not mention the visit unless the workspace turned citeVisits on.
| Name | Type | Req | Description |
|---|---|---|---|
| buyingPagesOnly | boolean | – | – |
| limit | integer | – | – |
| minStrength | integer | – | – |
| periodDays | – | – | – |
No output schema declared.
No examples provided.
motor_report Ver o relatório por motor ~283
Reports the results of each outreach campaign in the workspace (people contacted, replies, meetings, credits spent); Nock calls each campaign with its signals a "motor", a prospecting playbook. Read-only. How the motors are doing ("como estão os motores?"): every campaign of the workspace as a motor, for the last 7, 30 or 90 days. Per motor: people added, people first contacted in the period, replies, positive replies (null while replies are not classified), meetings (null when the workspace never recorded one), credits spent, credits per positive reply, and the reply rate by channel (e-mail vs LinkedIn). Rates are percentages of the people first contacted in the period. Also the reply and positive rates by signal family and by the most common signal combinations for people that came from compound signals; with fewer than 20 people a rate is left out and marked "amostra pequena" (never present it as a result). Targets: 5% replies, 2% positive; below 2% replies after 150 first touches the motor should be rewritten or turned off. When the weekly learning is on, `learning` has last week's verdict per motor and weight suggestions for compound blocks (never applied: only the user changes a weight). Free, reads only.
| Name | Type | Req | Description |
|---|---|---|---|
| days | – | – | Period in days; default 30. |
No output schema declared.
No examples provided.
phone_owner Confirmar o dono do número ~112
For B2B outreach: checks that a Brazilian mobile number found for a decision maker (in a sheet or a search) really belongs to that person, before a campaign writes to it, from the owner's name and e-mails the registry has for it. One number per call. Meant only for a business contact the user is already prospecting, not for identifying a private individual. Charged 10 credits only when a name comes back. It does not return a document number.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | – |
No output schema declared.
No examples provided.
preview_campaign_messages Escrever as mensagens da pessoa de exemplo ~145
Writes the messages of ONE example person of the campaign from its current template and returns them, to show how the template reads before the other people's messages are written again. Not read-only: the new messages replace that person's unsent ones (sent and hand-edited messages are kept). Nothing is sent to anyone. It picks the person itself (one with a buying signal when there is one) and keeps the saved messages, so they are not paid twice. A second call in the same conversation turn returns the first result. The result's messagesOutdated counts the other people whose messages still come from the earlier template. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | Exact campaign UUID. |
No output schema declared.
No examples provided.
qualify_sheet_leads Qualificar leads da planilha ~160
Score people in one owned sheet against the workspace ICP or an explicitly linked campaign audience, using the data and signals Nock already has. Returns fit, priority, coverage, status, evidence gaps and concise explanations per row. Use the active selected rowIds when present; omit rowIds only when the user means the whole sheet. This does not search LinkedIn, Reddit or the open web. Works on any sheet: only its people are scored; companies without a person are skipped.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | – | Campaign UUID only when the sheet is being qualified for that campaign. |
| rowIds | array | – | Optional exact row ids. Omit to qualify every row in the sheet. |
| sheetId | string | yes | Exact people-sheet UUID. |
No output schema declared.
No examples provided.
read_learn_article Ler tutorial da Nock ~98
Read Nock's own tutorials (the Aprender page): how something in Nock works, what it costs or where to find it. With slug: the whole tutorial. With query (or nothing): the tutorials that match, with their slugs. Each tutorial's page is /aprender/<slug>. Read-only, free.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
| query | string | – | – |
| slug | string | – | – |
No output schema declared.
No examples provided.
regenerate_outreach_cadence Regenerar textos da cadência ~125
Rewrites the open (unsent) cadence messages of people in ONE campaign with the AI writer, from the campaign's current template. It takes no instructions and does not change the template or a step's text or day. Steps that already sent, failed, or are mid-dispatch are kept. Optional prospectIds limit the rewrite to those people; without them everyone with unsent steps is refreshed. Nothing is sent. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | Exact campaign UUID. |
| prospectIds | array | – | When set, only these people are rewritten. |
No output schema declared.
No examples provided.
remove_cadence_rule Tirar regra de cadência ~94
Take one rule out of the workspace's cadence rules, for example a rule just kept from a cadence adjustment (its keptRules) that was meant for one campaign only or no longer holds. Takes the rule's text as it was kept. Campaigns already written keep their text; the next ones stop following it. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| rule | string | yes | The rule's text, as it is in the rules. |
No output schema declared.
No examples provided.
remove_knowledge_document Remover documento ~39
Remove one workspace document, by its id, from the workspace's knowledge base. It cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | – |
No output schema declared.
No examples provided.
rename_sheet Renomear planilha ~28
Rename one owned sheet.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| sheetId | string | yes | – |
No output schema declared.
No examples provided.
research_web Pesquisar na web ~181
Answers a free-form natural-language QUESTION about a single lead/company (e.g. "what does this company sell?", "recent funding?") with web research. Grounds the answer in the company's website when one can be resolved. The answer is AI-generated and may be uncertain; it costs credits. Returns a concise answer plus the source URL used.
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | – | Optional extra row columns used as research context, same as REST POST /api/research. |
| company | string | – | – |
| companyDomain | string | – | – |
| string | – | – | |
| headline | string | – | – |
| linkedinUrl | string | – | – |
| location | string | – | – |
| name | string | – | – |
| prompt | string | yes | The research question to answer about the lead. |
| role | string | – | – |
| website | string | – | – |
No output schema declared.
No examples provided.
restore_cadence_version Restaurar versão da cadência ~142
Puts an earlier cadence template back ("volta pro template que tava antes"). Without versionId it restores the most recent earlier version; versionId picks another. Steps already sent stay; people who have not received a step get the restored template, but their messages are not rewritten by this call: the result's messagesOutdated counts them and messagesNext describes the rewrite still pending. The restore itself is kept as a version, so it can be undone. Nothing is sent.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | Exact campaign UUID. |
| versionId | string | – | Optional version id from the campaign's cadence versions; omitted, the most recent earlier version. |
No output schema declared.
No examples provided.
restore_company_sheet Voltar a planilha de empresas ~55
Sheets hold people and companies together, so there is no conversion to undo: it changes nothing and says so.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | The user confirmed going back to the company sheet. |
| sheetId | string | yes | – |
No output schema declared.
No examples provided.
rewrite_campaign_messages Reescrever as mensagens da campanha ~103
Writes again the messages of the people of ONE campaign that are from an earlier version of its template (messagesOutdated), the "Reescrever as N" action. One run, only those people: sent messages and hand-edited ones stay. It is refused in the same request that changed the template. Free. Nothing is sent. Returns how many were rewritten, or that the rest is still being written.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | Exact campaign UUID. |
No output schema declared.
No examples provided.
run_sheet_ai_column Executar coluna de IA ~136
Runs one already-configured AI or web-research column and saves a generated value for each requested row. Takes the column's exact ai: id and, optionally, the rowIds to run. It costs 1 credit per row for an AI column and 6 per row for a web-research column (aiKind "web", which reads the company's site and searches the web, citing its source); the column's creditsPerRow says which. The result's creditsCharged says how many were spent.
| Name | Type | Req | Description |
|---|---|---|---|
| columnId | string | yes | – |
| rowIds | array | – | – |
| sheetId | string | yes | – |
No output schema declared.
No examples provided.
run_sheet_enrichment Executar enriquecimento da planilha ~268
Run one already-configured enrichment column and persist its waterfall results in the sheet. Takes the exact enrichment column id (as the sheet's rows list it) and optionally the row ids to process; without them, the first 25 rows that have any value. For several columns pass columnIds: they run in order, company domain, LinkedIn, work e-mail, then phone or WhatsApp, each reading what the one before found. A contact's reveal column id (system:reveal:linkedinUrl, system:reveal:email or system:reveal:phone) runs that contact's enrichment column, added first when the sheet has none. Can spend enrichment credits; the result's creditsCharged says how many.
| Name | Type | Req | Description |
|---|---|---|---|
| columnId | string | – | One enrichment column, or a contact column's revealColumnId. Use columnIds for several. |
| columnIds | array | – | Several enrichment columns, run in dependency order (domain, LinkedIn, e-mail, phone). |
| confirmed | boolean | – | True only after the user said yes to this run's quote. |
| force | boolean | – | Look up again the rows that already hold the field. Only on the user's explicit ask. |
| rowIds | array | – | – |
| sheetId | string | yes | – |
No output schema declared.
No examples provided.
run_signal_monitor Rodar monitoramento ~37
Run a signal monitor now instead of waiting for its schedule. Spends from its monthly credit limit.
| Name | Type | Req | Description |
|---|---|---|---|
| monitorId | string | yes | – |
No output schema declared.
No examples provided.
save_memory Guardar memória do Nock Agent ~93
Keep something the user asked to be remembered ("lembra que...", "a partir de agora...") for every later conversation. One sentence each, in their words. Not for the company profile (what it sells, the ICP) nor for how messages must read ("nunca fale de preço", "sempre em português"): those are kept in the knowledge base and the cadence rules.
| Name | Type | Req | Description |
|---|---|---|---|
| memories | array | yes | – |
No output schema declared.
No examples provided.
save_outreach_template Salvar template de prospecção ~233
Create or update one outreach template for the authenticated user. Without templateId the template is saved by name (an existing template with the same name is overwritten with the new values instead of duplicated). With templateId the named template is patched, which is the only way to rename it; the fields passed replace the saved ones and omitted fields keep their current value. An overwritten value cannot be recovered. Nothing is sent.
| Name | Type | Req | Description |
|---|---|---|---|
| businessContext | string | – | Company/product context (plain text or markdown) used to ground every generated message. |
| campaignName | string | – | Default campaign name suggested when this template is used. |
| language | string | – | Language to write in. Defaults to "Português (Brasil)". |
| name | string | – | Template name. Required when templateId is omitted. |
| offering | string | – | What the sender offers, in the sender's own words. Required when templateId is omitted. |
| senderName | string | – | – |
| templateId | string | – | Exact template UUID to patch. |
| tone | string | – | Desired tone, e.g. "direto e consultivo". |
No output schema declared.
No examples provided.
search_companies Buscar empresas ~2,313
Searches for COMPANIES matching filters such as name, industry, keywords, size, location or businessModel (b2b or b2c). Brazilian searches also support the public company registry: CNAE (activity code), Receita status, headquarters/branch, fiscal size, social capital, legal nature, Simples, opening period, partner name and presence of phone or email. A Brazilian company is identified by its CNPJ, the public company registration number the Receita Federal publishes (like a US EIN): it identifies a company, not a person, and is not a personal document. Common activity terms are mapped deterministically to CNAEs. Returns candidate companies (target accounts) with all fields supplied by the selected source. Metered: credits are charged per delivered result. When the first source returns too few results, one fallback attempt with another source runs automatically. Results shown as tables are quality-reviewed and may also replace rejected rows through another source.
| Name | Type | Req | Description |
|---|---|---|---|
| activityLevels | array | – | Activity level the Nock computes from signals it already has (site up, job openings, news, registry status, phone), e.g. ["high", "medium"] for "empresas ativas de verdade". Rows without a level are… |
| branchesMin | integer | – | At least this many active branches (filiais) under the same CNPJ root, e.g. 5 for "redes com 5 filiais ou mais". Only with state, city or CNAE, only when asked. |
| businessModel | string | – | Keep only companies that sell to businesses (b2b) or consumers (b2c), decided from the CNAE division. Mixed or unknown CNAEs are excluded. |
| capitalMax | number | – | Maximum social capital in BRL. |
| capitalMin | number | – | Minimum social capital in BRL. |
| city | string | – | Brazilian municipality, e.g. "Curitiba". A state is not needed: a name only one state has is searched there, and a name several states share ("Bom Jesus") is searched in all of them, with searchNotes… |
| cnaes | array | – | Brazilian CNAE codes, digits only, e.g. ["6920601"]. |
| companyOrder | array | – | Optional provider priority. Omitted providers keep their default order. Omit the field to use the dashboard's configured default order. |
| currentRegimes | array | – | Current tax regime to keep: mei, simples, lucro_presumido, lucro_real. A regime filter; a company whose regime is unknown is left out. |
| emailValidated | boolean | – | Only companies whose registered e-mail is confirmed: published by the company or found on a public source, with a domain that receives mail. For "e-mail validado". Only when asked. |
| employeesMax | integer | – | Maximum estimated employees of the Brazilian establishment (CNPJ), from public data. Needs state, city or CNAE. Only when asked. |
| employeesMin | integer | – | Minimum estimated employees of the Brazilian establishment (CNPJ), from public data. Not companySize (LinkedIn headcount of the whole company). Needs state, city or CNAE. Only when asked. |
| establishmentTypes | array | – | Whether Brazilian establishments are headquarters or branches. |
| exactNameLookup | boolean | – | Set true only when resolving one explicitly named company. Keep only signals the user actually supplied, such as its name, sector and location; placeholder registry values are removed by the runtime. |
| excludeDomains | array | – | Company domains already delivered in earlier turns. They are excluded before billing so a request for more companies returns only new candidates. |
| excludeNames | array | – | Company names already delivered in earlier turns. Pass them with excludeDomains when fulfilling a request for more companies. |
| excludeProviders | array | – | Providers to skip for this search. Use when the user explicitly asks for another data source or prior results from those providers were duplicates. |
| fiscalSizes | array | – | Brazilian fiscal-size IDs: 01 unknown, 02 ME, 03 EPP, 05 demais. |
| governmentSalesMin | number | – | Public contracts of the company in the last 24 months adding up to at least this many BRL, e.g. 1000000 for "já recebeu mais de R$ 1 milhão do governo". Needs state, city or CNAE. Only when asked. |
| hasEmail | boolean | – | Require a public registry email address. |
| hasPhone | boolean | – | Require a public registry phone number. |
| hasWebsite | boolean | – | Only companies with their own website (domain), from any source. |
| headcountGrowthMin | number | – | Team grew at least this many percent (LinkedIn headcount), e.g. 20 for "cresceu 20% em 6 meses". Only companies with a LinkedIn page; for small businesses use sectorGrowth. Only when asked. |
| headcountGrowthMonths | – | – | The window of headcountGrowthMin: 6 (default) or 12 months. |
| immediateRegions | array | – | IBGE região geográfica imediata codes (6 digits), e.g. ["410001"]. Only when the person names one. |
| industry | string | – | Industry, e.g. "saas" or "fintech". |
| intermediateRegions | array | – | IBGE região geográfica intermediária codes (4 digits), e.g. ["4101"]. Only when the person names one. |
| keywords | array | – | Search terms, e.g. ["B2B SaaS", "BPO financeiro"]. |
| legalNatureCodes | array | – | Brazilian legal-nature codes, e.g. ["2062"] for Sociedade Limitada. |
| limit | integer | – | Exact requested result count (<=20). Omitted, the default count. |
| location | string | – | Location, e.g. "United States". |
| mesoRegions | array | – | IBGE mesorregião codes (4 digits), e.g. ["4110"]. Only when the person names a mesorregião. |
| microRegions | array | – | IBGE microrregião codes (5 digits), e.g. ["41037"] for Curitiba. Only when the person names a microrregião. |
| name | string | – | Company name, e.g. "Acme". |
| neighborhoods | array | – | Brazilian neighbourhoods (bairros), e.g. ["Batel"]. Only with city or state, only when asked. |
| openingDateMax | string | – | Latest opening date (YYYY-MM-DD). |
| openingDateMin | string | – | Earliest opening date (YYYY-MM-DD). |
| partnerDocument | string | – | Partner/shareholder CPF or CNPJ; punctuation is accepted. |
| partnerName | string | – | Partner/shareholder name. |
| phoneScoreMin | integer | – | Minimum reliability of the company's registered phone, 1 to 5, scored by the Nock from what it already has (valid number, not shared with another company or the accountant, active and recent registry… |
| phoneType | string | – | Receita phone is a mobile (celular) or a landline (fixo). Only when asked. |
| productKeywords | string | – | Words in the company's products and services, comma-separated terms, e.g. "cerveja artesanal, chope". Matched on site text the Nock already read and on the CNAE descriptions; a row with neither is le… |
| radius | object | – | Companies whose CEP is within km of a reference CEP (or point). Needs state, city or a region. For companies near a place (perto de, raio de X km). |
| registrationStatuses | array | – | Brazilian Receita registration statuses. |
| revenueMax | number | – | Maximum Faturamento estimado in BRL a year, the same estimate. Applied by the registry with a state, city or CNAE. |
| revenueMin | number | – | Minimum Faturamento estimado in BRL a year (R$ 500 mil per month is 6000000). An estimate per CNPJ from public data (estimated employees x the sector's revenue per person, capped by the tax regime's… |
| schoolEnrollmentMax | integer | – | Schools with at most this many students. Only when asked. |
| schoolEnrollmentMin | integer | – | Schools with at least this many students in basic education (matrículas), e.g. 300 for "escolas com mais de 300 alunos". Only when asked. |
| schoolNetworks | array | – | Schools in activity in the Censo Escolar (INEP) of these networks, e.g. ["privada"] for "escolas privadas" or "colégios particulares". The CNPJ is the school's own, else its mantenedora's; the decisi… |
| schoolStages | array | – | Schools offering any of these stages, e.g. ["medio"] for "ensino médio", ["fundamental_iniciais", "fundamental_finais"] for "ensino fundamental", ["creche", "pre_escola"] for "educação infantil". Onl… |
| sectorGrowth | array | – | Job growth of the company's main sector in its city over 12 months, from public employment data, e.g. ["strong_growth", "growth"] for "setor em crescimento na região". Needs state, city or CNAE. Only… |
| sellsToGovernment | boolean | – | true keeps companies with a public contract with the government (any sphere) in the last 24 months, for "vende para o governo" or "fornecedores de prefeituras". Needs state, city or CNAE. Only when a… |
| showResults | boolean | – | Optional interactive-table presentation hint for in-product Agents. |
| simpleOption | boolean | – | Whether the company opted into Simples Nacional. |
| sizes | array | – | Headcount buckets as "min,max" ranges, e.g. ["51,200"]. |
| state | string | – | Brazilian state code, e.g. "PR". |
| statesMin | integer | – | Active establishments in at least this many Brazilian states, e.g. 3 for "atua em 3 estados". Only with state, city or CNAE, only when asked. |
| useBrazilianRegistryFilters | boolean | – | True turns on the Brazilian registry filters: CNAE, Receita status, headquarters/branch, fiscal size, legal nature, partner, Simples, opening date, phone/email presence, social-capital, IBGE region,… |
No output schema declared.
No examples provided.
search_people Buscar pessoas ~2,042
Search for PEOPLE (potential leads) matching filters such as job title, seniority, company, CNPJ, industry, location or a buyingSignal (hiring, funding, news, job_change, tech, cnpj, crm, visitor, any). Company discover uses the enabled signal sources. job_change is company hire/promote/leave news when those domains exist; otherwise it searches person movers in the last 90 days through enabled sources. A campaign job_change gate also lets a fresh person move through. tech needs technologies[] (job-post evidence first, then site technology detection); cnpj uses the Brazilian registry; crm uses closed-lost deals and champions who left in the connected HubSpot or Salesforce; visitor uses identified visits already on inbound sheets. People are then searched at those companies. Returns a list of candidate people with name, headline, company and (when available) email and LinkedIn URL, for building a prospect list from criteria. Metered per delivered result: each search spends credits. In-product Agent searches automatically make one provider-fallback attempt when the first cascade returns fewer rows than requested. Searches shown as tables are quality-reviewed and may also replace rejected rows through another provider. page pages through results with the same filters; an empty page means there are no more, and pages may overlap. Every result carries funnel (requested, found, kept, removed by reason: same_company, outside_sector, registry_mismatch, customer and others) and funnelText, one plain sentence of it. Lists across companies keep one person per company unless peoplePerCompany is set. A CNAE or another Receita filter is exact only on rows with a CNPJ: on rows without one a CNAE is approximated by the company's industry (filterReport.registry counts each way). Near misses (sector not confirmed) are counted in nearMisses, held back and not charged; with includeNearMisses they come after the full matches, each marked nearMiss. limit goes up to 200: the search reads…
| Name | Type | Req | Description |
|---|---|---|---|
| buyingSignal | string | – | Buying signal, last 90 days. hiring: open roles from enabled signal providers. funding: a recent raise. news: company news. job_change: company hire/promote/leave news when discover finds domains; ot… |
| cnaeCodes | – | – | Receita activity codes (CNAE, 4 to 7 digits) the person's company must have. Only when asked. |
| cnpj | string | – | Restrict to one Brazilian company by CNPJ. Punctuation is accepted; digits are used. |
| company | string | – | Restrict to a specific company name. |
| companyAgeMaxYears | – | – | Company opened at most this many years ago. Only when asked. |
| companyLocation | string | – | Company headquarters only when the user explicitly asked for HQ. For city/country asks such as 'em São Paulo', use location instead — an HQ-only filter turns off the sources that search by the person… |
| companyRevenueMax | – | – | Maximum Faturamento estimado of the person's company in BRL a year, the same estimate and rule. |
| companyRevenueMin | – | – | Minimum Faturamento estimado of the person's company in BRL a year (R$ 500 mil per month is 6000000), an estimate per CNPJ from public data, not the declared figure. The people sources have no revenu… |
| companySizes | array | – | Headcount buckets as "min,max" ranges, e.g. ["51,200","201,500"]. |
| confirmed | boolean | – | true runs a search whose quote (status quote) the user accepted. |
| domain | string | – | Restrict to a company domain, e.g. acme.com. |
| excludeProviders | array | – | Providers to skip for this search. Use only when the user explicitly asks for another data source or prior results from those providers were duplicates. |
| founder | boolean|null | – | true: the person is a partner in the company's Receita record. Only when asked. |
| hiringTitle | string | – | Open role to discover companies hiring for, as the client says it (e.g. Head de Vendas, Gerente de Marketing); the search covers the role's family in Portuguese and English, so no exact title is need… |
| includeNearMisses | boolean | – | true adds the near misses a previous result counted (nearMisses) after the full matches, each marked nearMiss and charged like any delivered row. |
| industry | string | – | The company's industry, e.g. "fintech". Matched against a fixed taxonomy: a value outside it is DROPPED rather than applied, and the result then carries a `warnings` entry naming the filter and sugge… |
| jobTitle | string | – | Job title(s), comma-separated, e.g. "VP Sales, Head of Growth". Acronyms like "CTO" or "VP" are auto-expanded, but for broad seniority searches prefer the `seniorities` filter (c_suite, vp, director,… |
| languages | – | – | Languages the person speaks. Only when asked. |
| limit | integer | – | How many people to find, 1 to 200 (default 10). |
| location | string | – | Person location, e.g. "São Paulo" or "Germany", for a city or country. Setting companyLocation to the same place as well is redundant. |
| niche | string | – | A standing audience whose companies are resolved BEFORE the people search. shopping_centers is for shopping-mall decision makers: that segment has no industry of its own, and filtering by real estate… |
| page | integer | – | One-based result page. In Deep Mode, increment this only after the prior page was returned; keep every other filter unchanged and deduplicate results. |
| pastCompanies | – | – | Companies the person worked at before. Only when asked. |
| peoplePerCompany | integer | – | People per company in a list across companies, 1 to 10. Default 1, the best decision maker. |
| personLocation | – | – | Where the person is (city, state or country; SP and Brasil work). Only when asked. |
| roles | array | – | Job function keywords such as ["sales","engineering"]. Founder, co-founder, entrepreneur or owner belong in jobTitle, not here. Unknown roles disable providers that cannot filter by role. |
| sellsTo | – | – | b2b or b2c: who the company sells to, from its CNAE. Only when asked. |
| seniorities | array | – | Seniority levels, e.g. ["vp","director","c_suite"]. Bare Portuguese "seniores" is ["senior","manager"], not ["senior"] — Use senior only for senior individual contributors; it does not include manage… |
| shareCapitalMin | – | – | Minimum share capital in BRL. Only when asked. |
| showResults | boolean | – | Optional interactive-table presentation hint for in-product Agents. |
| signalPeriodDays | integer | – | Only with buyingSignal funding: how many days back a round counts (default 90). Set it only after the user agreed to widen the period (180 or 365). |
| sourceOrder | array | – | Optional provider priority. Omitted providers keep their default order. Omit the field to use the dashboard's configured default order. |
| taxRegime | – | – | Receita size or tax regime (mei, me, epp, simples, lucro_real...). Only when asked. |
| technologies | array | – | Only with buyingSignal tech: the technologies whose adopters are discovered, e.g. ["hubspot"]. Not a people filter. |
| tenureMaxMonths | – | – | At most this many months in the current role. Only when asked. |
| tenureMinMonths | – | – | At least this many months in the current role. Only when asked. |
No output schema declared.
No examples provided.
select_sheet_rows Selecionar linhas da planilha ~136
Select rows in the currently open sheet so the dashboard shows them selected and the same row ids can be used for a campaign later: exact rowIds, or filters and/or search (the sheet's Filtrar and Buscar; every filter must hold), e.g. the rows from SP with no active campaign. Up to 5000 rows. This changes web UI selection only; it does not delete or modify data.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | – |
| rowIds | array | – | – |
| search | string | – | Free text over name, company, role and e-mail, without accents. |
| sheetId | string | yes | – |
No output schema declared.
No examples provided.
send_feedback Enviar feedback para a Nock ~320
Shares feedback about Nock with the Nock team: product feedback from the user (praise, a complaint, something missing) or something concrete observed in Nock that worked or failed (a tool returned wrong or empty data, a step was confusing, a result was great). Not for model behavior, the user's local environment, an unclear prompt, or a tool error that was recovered from. actor "human" is for the user's own words; "agent" for the client's observations. message and context are in the user's language. Free, no credits. Not a support channel: no ticket and no reply.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | – | "human" when the feedback is the user's own words; "agent" (default) for your own observation. |
| context | string | yes | What the user was trying to accomplish. Leave out sensitive business information, contact data, API keys and passwords. |
| feature_area | string | yes | The Nock area it is about: search (busca de pessoas e empresas), enrichment (enriquecimento), signals (sinais), campaigns (campanhas e cadências), inbox (caixa de entrada), sheets (planilhas), integr… |
| message | string | yes | What broke or worked, concrete and specific: the tool or screen, what was expected, what happened. |
| sentiment | string | yes | positive, negative or neutral. |
No output schema declared.
No examples provided.
send_prospect_step_now Enviar etapa agora ~87
Sends ONE step of ONE person's cadence right now, ahead of its schedule. This sends a real message to the prospect. Runs only with confirmed: true. stepIndex is the 0-based position in that person's cadence.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | The user explicitly confirmed this send. |
| prospectId | string | yes | Exact prospect UUID. |
| stepIndex | integer | yes | – |
No output schema declared.
No examples provided.
send_to_webhook Enviar para webhook salvo ~311
POST JSON to a webhook SAVED in this workspace (n8n, Make, Zapier or the user's own system), once, now. It only sends to webhooks saved in Integrações e MCP → API e webhooks: takes the saved webhook's name or id, not a URL; an address that is not saved is refused, and so is one that is not public https. Takes exactly one of: payload (a JSON object), sheetId (optionally with rowIds) to send that sheet's rows, or campaignId to send that campaign's people; a sheet or a campaign sends at most 500 rows. The receiver gets {id, type: "send_to_webhook", createdAt, workspaceId, data}, signed like the workspace's event webhooks (X-Nock-Signature). Returns the HTTP status and the start of the response. Data leaves Nock to that receiver. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | – | Send this campaign's people. |
| payload | object | – | A JSON object to send as `data`. Omit when sending a sheet or a campaign. |
| rowIds | array | – | With sheetId: only these rows. Omit for the whole sheet. |
| sheetId | string | – | Send this sheet's rows, each as {rowId, <column label>: value}. |
| webhook | string | yes | The saved webhook's name or id, as listed in Integrações e MCP → API e webhooks. |
No output schema declared.
No examples provided.
set_autonomy_level Definir autonomia do Nock Agent ~200
Set how much the Nock Agent does alone for one action type in this workspace: 1 only tells (default), 2 suggests and does it with one tap, 3 does it and tells after. Whatever the level, the Agent still waits for approval before spending above a routine's credit cap, deleting, messaging leads with a cadence nobody approved, or touching billing. Only for an explicit request naming the change; never raise it from a complaint or a vague request. Raising takes two calls: with confirmed false it saves nothing and returns a quote ("Vou deixar X no nível N: ... Confirma?"); with confirmed true, only after the user's explicit yes to that quote, it saves. Lowering saves at once.
| Name | Type | Req | Description |
|---|---|---|---|
| actionType | string | yes | – |
| confirmed | boolean | – | Raising only: false (or absent) to get the quote; true only after the user said yes to it. |
| level | integer | yes | – |
No output schema declared.
No examples provided.
set_campaign_daily_people Pessoas por dia da campanha ~198
Changes how many new people an active campaign adds each day (0 turns daily additions off; at most 500). It authorizes spending every day, so it takes two calls: the first, with confirm false, only returns the new monthly credit ceiling and changes nothing; a call with confirm true and that same monthlyCredits applies it. Only a workspace owner or admin can change it. This is people added per day, not a sending limit: each account still sends within its own limits (LinkedIn about 30 a day per account), so people beyond what the accounts send wait in the cadence, and sendingNote says so. When the result has cappedAt, the workspace still takes at most that many a day.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | – |
| confirm | boolean | yes | – |
| monthlyCredits | integer | – | The ceiling the first call returned, echoed on the confirming call. |
| peoplePerDay | integer | yes | – |
No output schema declared.
No examples provided.
set_campaign_signal_monitor Campanha alimentada por monitor ~377
Feeds a campaign from a market or social signal monitor, or stops every signal with monitorId null. Without add or replaces the monitor becomes the campaign's only signal. Every signal of a campaign delivers into the campaign's one sheet (what it delivered elsewhere is copied in). A campaign takes up to 5 signals: add true keeps the others and adds this one; replaces (a monitorId the campaign has) puts this one in its place and pauses the old one when no other campaign reads it. Each day the campaign's daily additions take the companies the signals delivered and write to one person at each: the person the monitor already found, a store's owner, or jobTitle searched at the company (required unless the monitor is about online stores or the campaign already has a job title; with add the campaign keeps its own). People are added, and charged, at the campaign's daily people limit. On an active campaign, add or replaces turns the signal on and it spends credits every day: the first call returns status quote with the monthly credit ceiling and changes nothing; the call with confirmed true applies it. Only a workspace owner or admin can change it.
| Name | Type | Req | Description |
|---|---|---|---|
| add | boolean | – | true: keep the campaign's other signals and add this one. |
| campaignId | string | yes | – |
| confirmed | boolean | – | true only after the user agreed to the monthly cost a quote returned. |
| jobTitle | string | – | – |
| monitorId | – | yes | – |
| replaces | string | – | A signal of the campaign that this monitor takes the place of. |
| runBeforeActive | boolean | – | On a campaign that is not active: true runs the signal now (it spends and its companies wait for the activation), false runs it only once the campaign is activated. Only what the person chose in the… |
No output schema declared.
No examples provided.
set_prospect_closure_reason Registrar motivo de encerramento ~74
Record why a conversation with ONE person ended (interested, not_interested, bad_timing, has_solution, wrong_person, opt_out), or null to clear it. Kept as history; it does not send anything.
| Name | Type | Req | Description |
|---|---|---|---|
| prospectId | string | yes | Exact prospect UUID. |
| reason | – | yes | – |
No output schema declared.
No examples provided.
set_routine_status Pausar ou retomar rotina ~50
Pause a routine, or resume it (it runs again at its next slot, never the ones it missed).
| Name | Type | Req | Description |
|---|---|---|---|
| routineId | string | yes | Exact routine id. |
| status | string | yes | – |
No output schema declared.
No examples provided.
update_cadence_ai_field Mudar a instrução de uma frase da cadência ~448
Changes the instruction of one sentence the Agent writes for each person in ONE campaign's cadence (a field marked {{ia:key}} in the bodies, shown on screen by its label, such as 'a vaga aberta' or 'a retomada'), for everyone on the list: how that sentence should read for all people ('na abertura, começa com "vi que vocês abriram vaga de X"', 'na vaga aberta, cita o cargo da vaga', 'a retomada não pode falar de preço'), including an edit made in one person's messages that should apply to everyone. A campaign's aiFields list each field's day, key, label, instruction and example. instruction is the whole instruction the field follows from now on: the current one with the requested change worked in, keeping what it says, from which fact, and what it leads into, unless that is what changes. example, when the request changes how the sentence reads: the current example rewritten to follow it, with the same facts. The instruction changes now, without writing anyone: in steps not sent yet, a sentence written from the old instruction goes back to the field, and nobody's messages are written again until a rewrite is requested (messagesNext in the result says how); messages edited by hand and sent ones stay; people not written yet follow it when written. Free. Nothing is sent. Not for fixed text or for how the whole cadence reads, and not meant for a campaign draft still being created in the web app's chat flow, which has its own draft editor.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | Exact campaign UUID. |
| day | integer | – | Only the field on this day's step, when the same field sits in more than one step and the user named one. Omit to change it in every step it is in. |
| example | string | – | A new example sentence that follows the new instruction; blank keeps the current one. |
| field | string | yes | The field's key ('abertura', 'retomada') or its label as the screen shows it ('a vaga aberta'). |
| instruction | string | yes | The field's whole new instruction, in the campaign's language. |
No output schema declared.
No examples provided.
update_campaign_audience Quem a campanha contata ~153
Changes whom a campaign contacts: the job titles of the person at each company (one per item), the sectors, the company sizes and the place. Only the fields sent change. The next daily run searches with them and the signals feeding the campaign look for the new titles; people already in the campaign stay. Free. Only a workspace owner or admin can change it.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | – |
| companySizes | array | – | Employee bands, e.g. "201,500". |
| industries | array | – | – |
| location | – | – | City, state or country; null clears it. |
| titles | array | – | The decision maker's titles, one per item, no commas inside a title. |
No output schema declared.
No examples provided.
update_campaign_settings Editar regras da campanha ~1,090
Changes a campaign's sending rules; only the fields sent change. approveBeforeSending can only be turned on here (every step then waits for approval in the Inbox); turning it off, and the daily enrollment, are authorizations given in the campaign's Settings screen. Turning off blockActiveSequence or blockContactedBefore returns a warning with what the campaign then lets in. Free, except that onlyActiveLinkedin on then costs 2 credits per person read before their first message. WhatsApp: whatsappMode (auto from the campaign's numbers, or task for the SDR), the numbers after the campaign's own, and who gets the leads' tasks (the lead's Responsável, or a rodízio among SDRs). manualLinkedin: every LinkedIn step becomes a task in the Inbox the owner does by hand. Nothing is sent.
| Name | Type | Req | Description |
|---|---|---|---|
| approveBeforeSending | boolean | – | – |
| blockActiveSequence | boolean | – | On by default: nobody in another active or paused campaign joins this one. false includes them on purpose, and they get both cadences at once. |
| blockContactedBefore | boolean | – | On by default: people already contacted (deleted campaigns too) are skipped. false contacts them again on purpose. |
| campaignId | string | yes | Campaign id. |
| duplicateProtection | boolean | – | Cancel repeated recipients and skip people already in the campaign. |
| emailOnlyWithoutLinkedin | boolean | – | A cadence with LinkedIn and e-mail steps reaches each person by one: LinkedIn steps when they have a profile, the e-mail steps only when they have none. People need one of the two to join, not both. |
| extraLinkedinAccountIds | array | – | Other connected LinkedIn accountIds the campaign's new invites go out from, in order, when its own account has no room today. Someone's later messages stay with the account that invited them. [] clea… |
| extraMailboxIds | array | – | Other connected Gmail mailbox ids, a teammate's too, someone's first e-mail goes out from, in order, when the campaign's own mailbox has no room today. Their later e-mails stay with that mailbox. []… |
| extraWhatsappAccountIds | array | – | Other WhatsApp number accountIds after the campaign's own, in order; someone who got a message stays on that number. [] clears. |
| fixSenderNames | boolean | – | Replace another sender's name in a message with the account that sends it. |
| holdOnOutOfOffice | boolean | – | An out-of-office reply holds the next message instead of ending the sequence. |
| linkedinDailyLimit | integer | – | LinkedIn invites and messages this campaign sends a day (default 20). LinkedIn only: e-mails of the cadence never count. The most depends on the account: 30 a day for most workspaces (a higher number… |
| manualLinkedin | boolean | – | LinkedIn done by hand: every LinkedIn step (invite, message, like) becomes a task in the Inbox with the text ready; Nock sends nothing on LinkedIn and needs no LinkedIn account. Turn it on when the u… |
| onlyActiveLinkedin | boolean | – | Only people active on LinkedIn in the last 2 months (a post, comment or reaction in 60 days) get the first message of a cadence with LinkedIn steps; the rest are held as "perfil inativo no LinkedIn".… |
| priority | boolean | – | Give this campaign priority: its due steps go out before those of the workspace's other campaigns, so it uses the shared LinkedIn quota first. Only one campaign has priority; turning it on here takes… |
| resumeAfterOutOfOffice | boolean | – | Resume the day after the return date in the auto-reply. |
| skipNationalHolidays | boolean | – | On by default: on Brazil's national holidays (Carnaval, Sexta-feira Santa and Corpus Christi included, in the campaign's time zone) the campaign sends nothing on any channel, and the steps go at the… |
| whatsappDistribution | string | – | owner (default): each lead's Responsável gets its tasks. round_robin: each lead without a Responsável goes to the next SDR of whatsappRoundRobinMembers; turning it on deals the leads already without… |
| whatsappMode | string | – | task: each WhatsApp step is a task the lead's Responsável sends from their own phone. auto: sent from the campaign's connected WhatsApp numbers (only when the workspace has automatic WhatsApp numbers… |
| whatsappRoundRobinMembers | array | – | The rodízio's SDRs in order (a member's name, e-mail or user id), the whole list. |
No output schema declared.
No examples provided.
update_campaign_signals Sinais da campanha ~234
Changes the signals that already feed a campaign. remove takes one off: it is paused when no other campaign reads it, and the people it brought stay. match any ("qualquer sinal") lets each signal bring companies on its own; match all ("todos os sinais") keeps only the companies every signal brought, each within its own window. feedOn false pauses every signal of the campaign; feedOn true turns them back on. On an active campaign, feedOn true turns paused signals on and they spend credits every day: the first call returns status quote with the monthly credit ceiling and changes nothing; the call with confirmed true applies it. Only a workspace owner or admin can change it.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | – |
| confirmed | boolean | – | true only after the user agreed to the monthly cost a quote returned. |
| feedOn | boolean | – | false pauses the campaign's signals; true turns them back on. |
| match | string | – | any = "qualquer sinal"; all = "todos os sinais". |
| remove | string | – | A signal (monitorId) to take off the campaign. |
No output schema declared.
No examples provided.
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
claude mcp add --transport http com-usenock-nock 'https://api.usenock.com/mcp'
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.