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 →
accept_received_invitation Aceitar convite no LinkedIn ~70
Accepts ONE LinkedIn connection request that the user's connected LinkedIn account received. It acts on the user's own LinkedIn account and runs only with confirmed true. One invitation per call.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | – | – |
| confirmed | boolean | yes | – |
| invitationId | string | yes | – |
No output schema declared.
No examples provided.
activate_outreach_campaign Ativar cadência de prospecção ~476
Activate the cadence of ONE draft campaign. Fills the campaign's cadence template with each person's name, company, role and signals into its steps (by default a LinkedIn connection and message first, then e-mail, alternating) to go out through the selected connected Gmail, LinkedIn and/or WhatsApp accounts. When several accounts are connected on a channel, the account id for that channel is required. A reply stops the person's remaining steps. Activating here does not turn on automatic sending: unless the campaign already has the owner's authorization, every message waits for approval in the Inbox, and "Aprovar antes de enviar" is saved on. Automatic sending is an authorization given only in the campaign's Settings screen, by the workspace's owner or an admin. The result says which applies (automaticSending; when false, approval and settingsUrl, the link to that screen). A campaign already authorized can send immediately inside the business window. When the campaign has people whose messages come from an earlier version of the template (messagesOutdated), activating first writes those people's messages again and then activates; rewrittenBeforeActivation in the result reports it. When people of the campaign still wait on their sheet row's e-mail, LinkedIn or phone lookup, enrichmentPending counts them by field and enrichmentPendingNote is a short sentence saying so; the address joins the campaign by itself when the lookup finishes. With no LinkedIn nor e-mail connected it still activates: waitingForChannel true means the campaign is active and waiting for a channel ("Ativa, esperando canal"); nothing is sent and no credit is spent until LinkedIn or an e-mail is connected (connectUrl), and then it starts sending on its own.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | Exact draft campaign UUID. |
| channels | array | – | Connected channels the user explicitly approved. Omit for a campaign of WhatsApp only: its steps are tasks the sender sends from their own phone, with no account to connect. |
| linkedinAccountId | string | – | Connected LinkedIn accountId, required when several LinkedIn accounts are connected. |
| mailboxId | string | – | Connected Gmail mailbox UUID, required when several mailboxes are connected. |
| tone | string | – | – |
| whatsappAccountId | string | – | Connected WhatsApp accountId, required when several WhatsApp accounts are connected. |
No output schema declared.
No examples provided.
activate_prospect_channel Ativar canal da pessoa ~91
Look up the missing work e-mail (channel email) or LinkedIn profile (channel linkedin) of ONE person in a campaign and, when one is found, turn that channel on in the person's cadence. This call sends nothing; the cadence sends on its schedule. Charges enrichment credits only when a contact is found.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
| prospectId | string | yes | Exact prospect UUID. |
No output schema declared.
No examples provided.
add_cadence_rule Acrescentar regra de cadência ~138
Saves one workspace rule for how messages read, in the user's words: tone, wording, language, what never to claim, price, links, what to say first (e.g. "nunca fale de preço na primeira mensagem", "sempre em português", "não cite concorrentes"). Every cadence written afterwards follows it; existing cadences change only when rewritten. The number of steps, their days and channels are campaign settings, not rules. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| rule | string | yes | The rule as the user said it, one sentence. Keep where it applies when they said it ("nas frias", "na campanha X"). |
No output schema declared.
No examples provided.
add_enrichment_to_sheet Adicionar enriquecimento à planilha ~199
Adds and configures one field-specific enrichment column in a sheet the user owns. Inputs are bound to stable column ids, matching exact labels and source keys automatically. When no safe binding exists, it returns the available columns and adds nothing; a retry with inputBindings sets the binding. It configures the column but does not run it, so it spends no credits.
| Name | Type | Req | Description |
|---|---|---|---|
| employeeRole | string | – | role_employee ("Gestor por cargo") only, required there: the job to look for among the company's registered employees, e.g. "Gerente comercial", "Gerente de loja", "Diretor", "Comprador", "Gerente de… |
| fieldId | string | yes | – |
| inputBindings | object | – | Optional enrichment input key -> exact stable sheet column id. |
| sheetId | string | yes | – |
No output schema declared.
No examples provided.
add_knowledge_document Adicionar documento ~48
Add a text document to the workspace (a pitch, a case, a price list) so campaigns can use it.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
add_prospects_to_campaign Adicionar pessoas à campanha ~351
Add people from a people sheet to an existing campaign. Fills the campaign's cadence template with each person's name, company, role and signals. Skipped: rows already in the campaign; people the user's connected CRM already has (the result's crmKnown, with crmKnownReason saying how many and why); and people the user removed from this campaign before (the result's removedBefore, with removedBeforeReason saying how many and who), unless includeRemoved is true. Every row asked for is added in this one call (up to 1000, in batches of 25); a campaign has no size limit. Without rowIds, adds the sheet's people rows not yet in the campaign. Only adds people already in a sheet; it does not search for new people. Ids must be exact; none are guessed. A campaign has one sheet: people from another sheet are copied into the campaign's sheet (the same person is never added twice) and point there. When people of the campaign still wait on their sheet row's e-mail, LinkedIn or phone lookup, enrichmentPending counts them by field and enrichmentPendingNote is a short sentence saying so; the address joins the campaign by itself when the lookup finishes.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | Exact campaign UUID. |
| includeRemoved | boolean | – | True brings back people previously removed from this campaign (the ones a result reported in removedBefore). Leave it out or false to skip them. |
| rowIds | array | – | Optional exact sheet row ids, up to 1000. Omit to add every people row of the sheet not yet in the campaign. |
| sheetId | string | yes | Exact people sheet UUID. |
No output schema declared.
No examples provided.
add_rows_to_sheet Adicionar linhas à planilha ~218
Add rows to ONE specific enrichment sheet owned by the authenticated user, by its exact sheetId. People and company search results can be passed exactly as returned; nested objects become flat columns. Keys may be stable column ids, semantic keys such as fullName/companyDomain, exact renamed column labels, or new field names. New fields become referenceable columns; matching people/companies keep their existing values while empty cells are completed from the new payload. Unchanged duplicates are skipped. The result includes the exact ids and labeled values of every newly added row so they can be used immediately. Any sheet takes both people and companies: a row that names someone (name, e-mail or LinkedIn) is a person and joins their company; a row with only a company is a company without a person, and a company already there is completed, never repeated.
| Name | Type | Req | Description |
|---|---|---|---|
| rows | array | yes | One to 25 people/company records to append, flat or as the people and company searches returned them. |
| sheetId | string | yes | Exact enrichment sheet UUID. |
No output schema declared.
No examples provided.
adjust_outreach_cadence Ajustar cadência da campanha ~387
Changes how ONE campaign's messages read from one sentence of the user ('não fala de preço na primeira mensagem', 'mais curto', 'sem link na primeira', 'muda o tom para mais direto') and writes its template again in the same shape, now (it takes a few seconds). The people's steps not sent yet take the new template; nobody's messages are written again until a rewrite is requested (messagesNext in the result says how); sent messages and hand-edited ones stay. What the instruction teaches about how messages read is kept by default: rules takes the style part of the instruction as one to three short imperative sentences in the user's words that hold for any campaign ('Abra com uma pergunta de sondagem.', 'E-mails com até cinco frases.'), saved as workspace cadence rules (de-duplicated) so every campaign written afterwards follows them; the result's keptRules says which were kept. campaignOnly true when the instruction is only about this campaign's own content (its offer, a subject line, a case, its audience): nothing is kept beyond it. forAll true saves it only as a workspace rule, not on the campaign. Free. Nothing is sent. 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. |
| campaignOnly | boolean | – | True only when the instruction is about this campaign's own content (offer, subject, case, audience), not how messages read. |
| forAll | boolean | – | True when the sentence is a rule for every campaign. Default false. |
| instruction | string | yes | What to change, in the user's words, one sentence. |
| rules | array | – | The style part as short imperative rules for any campaign, in the user's words. Kept as workspace cadence rules. |
No output schema declared.
No examples provided.
ai_column Gerar valor com IA ~225
Generate ONE terse value (a few words / one line) for a row, given that row's known fields and a natural-language instruction — the same "Usar IA" column available in Nock. Use for classification/extraction/summarization into a single cell. A question about facts of the row's company or person (sector, products, news, technology, size, funding) first reads the company's site and runs a short web search, and returns its sourceUrl: 6 credits. From the row's fields alone (classify, summarise, translate): 1 credit. evidence says which: web, row_only or none (nothing reliable found). web forces it either way.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | yes | The row's known fields, e.g. { "name": "...", "company": "..." }. |
| instruction | string | yes | What the column should contain, e.g. "the company's main product". |
| web | boolean | – | true: search the web first; false: the row's fields only. Default: decided by the instruction. |
No output schema declared.
No examples provided.
approve_inbox_message Aprovar e enviar mensagem ~99
Approves and sends the step waiting for approval in one Inbox conversation (campaigns set to approve before sending). This sends a real message to the prospect. Runs only with confirmed: true. stepIndex comes from the conversation's pendingApproval.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
| confirmed | boolean | yes | The user explicitly confirmed this send. |
| prospectId | string | yes | The conversation's prospectId. |
| stepIndex | integer | yes | – |
No output schema declared.
No examples provided.
assign_prospects Atribuir responsável ~251
Set who sends the WhatsApp tasks of people in ONE campaign: their owner ("Responsável"), a member of the workspace. With owner, the people in prospectIds go to that member (owner null takes it off: nobody). With distributeAmong, the people in prospectIds, or without prospectIds everyone in the campaign with no owner yet, are dealt in turn among those members (round-robin, oldest first). Members are named by first name, full name, e-mail or user id; a name that matches nobody, or more than one member, answers with the workspace's members and changes nothing. Only the WhatsApp tasks follow the owner: e-mail and LinkedIn keep going from the campaign's sender. Free, and nothing is sent.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | Exact campaign UUID. |
| distributeAmong | array | – | Members to deal the people among, in turn (names, e-mails or user ids). |
| owner | – | – | The member who gets them (name, e-mail or user id), or null for nobody. |
| prospectIds | array | – | The people to change. Required with owner; with distributeAmong, omit to deal everyone in the campaign without an owner. |
No output schema declared.
No examples provided.
brain_lookup Procurar no workspace ~134
Searches the user's own Nock workspace (not the web) for a company, a person or a subject, read-only, across everything at once: people in campaigns (status, last send, reply), campaigns, sheets (by name or a row that mentions it), signals, the company documents and saved memories. Answers questions about something by name ("tudo sobre a Acme", "o que aconteceu com o Marcos", "o que a gente já falou de escolas") in one search instead of listing campaigns or sheets one by one. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The name or subject, in the user's words. |
No output schema declared.
No examples provided.
brief_lead Resumo de pessoa e empresa ~192
The platform's person and company brief for one lead: who they are now (LinkedIn read today), their role at the company, what they post about, and their company (what it sells, customers, size, funding, open roles, key points, news, its posts, competitors). Takes an email, the person's LinkedIn URL, a company domain or the company's LinkedIn URL (any one is enough; more make it surer). Costs 22 credits when it finds something and takes about a minute; the same lookup is kept for 24 hours at no charge. For a brief, a summary or 'who is' a lead.
| Name | Type | Req | Description |
|---|---|---|---|
| companyDomain | string | – | – |
| companyLinkedinUrl | string | – | – |
| string | – | – | |
| personLinkedinUrl | string | – | – |
| refresh | boolean | – | Only for an explicit request to look it up again. |
No output schema declared.
No examples provided.
check_sheet_signals Checar sinais da planilha ~444
Which companies of a sheet (or of the rows given) show a buying signal, read and checked in one call, free: the signals the sheet already has (its Sinal column, an imported signal column, the ERP and loyalty club columns), the Receita's events of each CNPJ through the Nock Registry (filial nova, capital aumentou, sócio novo, contrato público, saída do Simples or MEI, periodDays 7/30/45/60/90, 90 by default), Nock's job index (openings in the period, and the ERP a post names as the company's) and the answers Nock already keeps (loyalty club, competitors' club apps, ERP). What fires is written into the sheet as its signal cells, on every row of the company. Returns, per signal, how many companies show it with examples (the fact and its public evidence) and the monitor that keeps bringing it (feed), plus companiesWithSignal, companiesWithoutSignal and signalRows. paidChecks (loyalty_club for supermarkets, erp) check the companies with no kept answer, up to 30 per call within the call's time: without confirmed they are only quoted (paidQuote.maxCredits, status needs_confirmation); with confirmed true they run, and only the companies where the signal is found are charged (4 credits a loyalty club answer, 6 an ERP proved).
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | – | true runs the paid checks a call without it quoted (paidQuote), with the same input. |
| paidChecks | array | – | Paid checks for the companies with no kept answer: loyalty_club (supermarkets: a competitor's club or none) and erp (the ERP the company runs). Quoted first; run only with confirmed. |
| periodDays | – | – | How far back a signal counts: 7, 30, 45, 60 or 90 days. Default 90. |
| rowIds | array | – | Only these rows' companies (the rows the person picked). Omit for the whole sheet. |
| sheetId | string | yes | The sheet's id. |
No output schema declared.
No examples provided.
check_whatsapp Checar WhatsApp ~162
For B2B outreach: tell which Brazilian business mobile numbers the user already has (a company's or a decision maker's, from a sheet or a search) have WhatsApp, so a campaign only writes on WhatsApp to numbers that can receive it. It returns only yes, no or unknown per number: no name, profile or message. Up to 100 numbers per call, in any format. Free: no credits are charged. People who enter a campaign with a WhatsApp step are checked on their own; this tool answers for numbers outside a campaign, or one a task still shows as not confirmed. has_whatsapp is null when the number is not Brazilian or could not be checked (never read null as no).
| Name | Type | Req | Description |
|---|---|---|---|
| numbers | array | yes | – |
No output schema declared.
No examples provided.
clean_phone Limpar telefone ~118
Fix the format of Brazilian business phone numbers the user already has (a company's or a contact's, e.g. from a sheet) for free: puts them as (DD) NNNNN-NNNN, adds the missing ninth digit of a mobile, and marks a number that cannot exist (an unknown area code, too short). kind is mobile or landline. Up to 500 numbers per call. Formatting only: nothing is looked up outside, and no owner, name or other data comes back.
| Name | Type | Req | Description |
|---|---|---|---|
| numbers | array | yes | – |
No output schema declared.
No examples provided.
company_group Ver grupo econômico ~218
The economic group of a Brazilian company by its CNPJ: the companies that control it (its partners that are companies, up to two levels) and the companies its group's head controls (subsidiaries and acquired companies that keep their own CNPJ), each with its CNPJ, legal name, main activity (CNAE) and status at the Receita (inactive ones flagged), plus the group's active factories. Free: registry lookups only. Also: how many active branches (filiais) the company has and in which states, and the companies that share partners with it (sócios em comum; linked, not necessarily controlled; the partner is never named). Answers questions about the head office CNPJ, a group's companies ("as filhas", "as compradas"), the branches, or whether a company is still active. Requires the CNPJ. The registry shows what the Receita has: foreign controllers and shareholders of an S.A. are not listed.
| Name | Type | Req | Description |
|---|---|---|---|
| cnpj | string | yes | The company's CNPJ, with or without punctuation. |
No output schema declared.
No examples provided.
company_products Ver produtos e SKUs da empresa ~172
What a Brazilian company sells and how much of it: products registered at the Anvisa across its economic group (registered foods such as supplements, and cleaning products) and the product pages of its own site (pass domain), the product kinds with their usual packaging, and a volume tier (alto, médio, baixo) with why. Free. Answers how many SKUs or products a company has, what kinds, or tiers brand owners by volume. The open data leaves out notified cosmetics, beverages and meat; then, without a site sitemap, the count is partial and the result says so instead of guessing a tier.
| Name | Type | Req | Description |
|---|---|---|---|
| cnpj | string | yes | The company's CNPJ, with or without punctuation. |
| domain | string | – | The company's site, e.g. ype.com.br, to count its product pages. |
No output schema declared.
No examples provided.
confirm_decision_maker Confirmar decisor de pequena empresa ~145
Records whether a decision maker returned by the small-business decision-maker lookup is right, wrong, or has left the business. Free. The verdict weighs on the confidence every workspace sees and, for 'left', the person is no longer offered; the evidence is kept.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| cnpj | string | – | – |
| name | string | – | – |
| person | string | yes | The decision maker as the small-business decision-maker lookup named them. |
| state | string | – | – |
| verdict | string | yes | right: it is them; wrong: it is not; left: they no longer work there. |
| website | string | – | – |
No output schema declared.
No examples provided.
create_outreach_campaign Criar campanha ~829
Generate one personalized outreach message per people-sheet row and save them as a new prospecting campaign. Takes the exact sheetId of a people sheet. Without rowIds, uses every people row in that sheet (up to 1000, added in batches of 25 within this one call). templateId must be the exact id of a saved template; otherwise the campaign is described inline with name, offering, goal and a concrete cta. goal is the campaign objective; conversion, with a concrete commercial next step in cta, fits a company that sells to businesses and has no campaigns yet. Every sheet column is used as labeled context. Campaign generation does not consume credits. The campaign is saved as a draft; nothing is sent. When people of the campaign still wait on their sheet row's e-mail, LinkedIn or phone lookup, enrichmentPending counts them by field and enrichmentPendingNote is a short sentence saying so; the address joins the campaign by itself when the lookup finishes.
| Name | Type | Req | Description |
|---|---|---|---|
| businessContext | string | – | Company/product context used to ground the generated messages. |
| cadence | array | – | Optional cadence steps, in the same shape as a campaign cadence update, a step's variantB (version B for an A/B test) included and saved with the exact text given. Omit to generate later. |
| constraints | string | – | Things the copy must never say or do. |
| cta | string | – | Desired next step: reply, book_call, accept_connect, share_resource, or custom text such as a demo or trial. Required and specific when goal is conversion. |
| give | string | – | Concrete value the sender can deliver before asking for the reader's time. |
| goal | string | – | Campaign objective: conversion, awareness, consultative, meeting, relationship, or custom text. conversion fits a workspace with no campaigns yet. |
| language | string | – | Defaults to the template language, or "Português (Brasil)". |
| linkedinAccountId | string | – | Connected LinkedIn accountId. |
| mailboxId | string | – | Connected Gmail mailbox UUID. |
| messageLength | string | – | – |
| name | string | – | Campaign name. Required unless the template supplies one. |
| offering | string | – | What the sender offers. Required unless the template supplies it. |
| rowIds | array | – | Optional. Exact row ids of that sheet. Omit to use every people row in the sheet (up to 1000). |
| senderCompany | string | – | Sender company name used in copy, same as REST senderCompany. |
| senderCompanyUrl | string | – | Sender company URL, same as REST senderCompanyUrl. |
| senderLinkChannels | array | – | Channels that may include the sender link: email, linkedin, whatsapp. |
| senderName | string | – | – |
| senderRole | string | – | Sender role used in copy, same as REST senderRole. |
| sheetId | string | yes | Exact people-sheet UUID. |
| signalGate | string | – | How to use company buying signals: personalize messages, or skip people missing the chosen signal. |
| templateId | string | – | Only the exact id of a saved outreach template. Omit when name and offering are set. |
| tone | string | – | Message tone, e.g. consultative, professional, friendly, direct. |
| whatsappAccountId | string | – | Connected WhatsApp accountId. |
| whatsappOnly | boolean | – | True for a campaign of WhatsApp only (the person picked WhatsApp alone): every step is a WhatsApp their sender sends from their own phone (tasks on the WhatsApp screen; Nock never sends it), no mailb… |
| whatsappStep | boolean | – | True adds one WhatsApp step near the end of the written cadence that the person's sender sends from their own phone (a task on the WhatsApp screen; Nock never sends it). Only for workspaces that have… |
No output schema declared.
No examples provided.
create_routine Criar rotina do Nock Agent ~388
Schedule something the Nock Agent does on its own, every week or every day ("toda segunda, ache 50 decisores novos e coloque na campanha X"), Brasília time. Actions: campaign_add_people (find count new people for a campaign from its search or signal), campaign_refill_from_signal (run the campaign's signal and add count people), campaign_status (pause or resume a campaign), sheet_enrichment (run an enrichment column on the rows that do not have it yet). Each run spends at most creditCap credits, doing fewer people or rows to fit; an empty creditCap means the full price of one run. What a run does depends on the workspace's autonomy level for that action: 1 only tells, 2 (default) suggests with a one-tap approval, 3 does it and tells after. Creating spends nothing. The campaign or sheet is the one passed; none is picked automatically. The result says what will run, when, and the cap.
| Name | Type | Req | Description |
|---|---|---|---|
| actionType | string | yes | – |
| campaignId | string|null | – | Exact campaign UUID, for the campaign actions. |
| columnId | – | – | Enrichment column id (as the sheet's rows list it), for sheet_enrichment. |
| count | – | – | People per run (1 to 50), for campaign_add_people and campaign_refill_from_signal. |
| creditCap | – | – | Most credits one run may spend. Empty: the full price of one run. |
| hour | integer | yes | Hour of the day, Brasília time (0 to 23). |
| name | – | – | Short name in the user's language. Empty: one is written from the schedule. |
| sheetId | string|null | – | Exact sheet UUID, for sheet_enrichment. |
| status | – | – | For campaign_status: paused to pause, active to resume. |
| weekday | string | yes | The day it runs, or every_day. |
No output schema declared.
No examples provided.
create_sheet Criar planilha ~124
Creates a NEW empty sheet owned by the authenticated user and returns its sheetId. Every sheet holds people and companies together: each row is a person with their company beside, or a company with nobody yet. mode is accepted and ignored. A sheet the user already has with the same name is returned instead of creating a duplicate. Sheets can be created here, not only in the dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | yes | 'people' for contact sheets, 'company' for organization sheets. |
| name | string | yes | Sheet name exactly as the user should see it in the dashboard. |
No output schema declared.
No examples provided.
create_signal_monitor Criar monitoramento ~1,741
Creates a signal monitor. Default: a MARKET monitor, with no source sheet: { mode: 'market', name, market: { category, ...filters }, dailyLimit }. Every day (or week) it searches the signal over that market and saves only companies it has not delivered yet into a companies sheet, created with the monitor's name unless destinationSheetId is given. Market categories: hiring needs hiringTitle, and industry keeps it to the ICP's sector in plain words; funding needs periodDays 7/30/90/180 and cnpj periodDays 7/30/45/60/90 (cnpj.event picks the registry event, opening by default); news needs categories and periodDays; location narrows it; tech is online stores by what their sites run (market.stores with platforms, crms, withoutCrms, noCrm, trafficTiers, states, city, companySizes, withDecisionMaker; only on workspaces that have the store search); custom is a very specific ask checked company by company (market { category: 'custom', source, rules }, the same source and rules format as the rules-based company search; every company is checked once; 2 credits per company checked plus 2 per company that passed); job_change is people new in a role, delivered into a people sheet (market { category: 'job_change', jobTitle, periodDays 30/60/90, location, industry, companySizes, domains, move }; 4 credits per person, no contact); construction is companies that registered a construction project at the Receita's CNO, "Iniciou uma construção" (market { category: 'construction', periodDays 7/30/90, location with a state, minAreaM2 optional }; 2 credits per company; cite Receita Federal (CNO)); growth is companies whose team grew (market { category: 'growth', minGrowthPct, months 6 or 12, location, industry, companySizes }; 2 credits per company); ads is companies running ads (market { category: 'ads', query } for a theme on Meta, or { category: 'ads', domains } for up to 10 accounts on Google; with start "future" only the ones that start advertising arrive; 4 credits per company); erp…
| Name | Type | Req | Description |
|---|---|---|---|
| monitor | – | yes | – |
No output schema declared.
No examples provided.
delete_outreach_template Excluir template de prospecção ~42
Delete ONE saved outreach template owned by the authenticated user. Campaigns already created from it are not affected.
| Name | Type | Req | Description |
|---|---|---|---|
| templateId | string | yes | Exact template UUID. |
No output schema declared.
No examples provided.
delete_prospect Excluir prospecção ~55
Delete ONE prospect owned by the authenticated user, including its messages and history. The campaign remains even if it has no people left. Irreversible: it cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| prospectId | string | yes | Exact prospect UUID. |
No output schema declared.
No examples provided.
delete_routine Apagar rotina ~83
Delete a routine for good. Two steps: with confirmed false it only returns which routine would be deleted and changes nothing; with confirmed true it deletes it, which cannot be undone. Pausing a routine is the reversible alternative.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | false to check; true only after the user said yes. |
| routineId | string | yes | Exact routine id. |
No output schema declared.
No examples provided.
delete_sheet Excluir planilha ~49
Deletes one owned sheet and all its rows. This cannot be undone. Requires confirmed: true.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | The user explicitly confirmed deleting this sheet. |
| sheetId | string | yes | – |
No output schema declared.
No examples provided.
discover_decision_makers Descobrir decisores ~277
Discover a specific decision-maker profile for companies in an owned sheet and add them to the same sheet, each as a person of their company; the company's row without a person becomes its first person. A dedicated multi-company action, separate from the enrichment-field catalogue. Uses all available company context (name, trade/legal name, domain, corporate email, CNPJ, partners, industry and location), takes the selected rowIds or, without them, the sheet's companies without a person (10 per call), and can also enrich requested contact fields. The owners profile uses CNPJ partners; functional profiles such as sales search matching job titles instead. destinationSheetId puts the people in another sheet.
| Name | Type | Req | Description |
|---|---|---|---|
| contactFields | array | – | Optional fields to enrich for each decision maker. |
| customJobTitles | array | – | Required job titles only when targetProfile is custom. |
| destinationSheetId | string | – | – |
| destinationSheetName | string | – | – |
| inferDomainFromCorporateEmail | boolean | – | – |
| quantityPerCompany | integer | – | – |
| rowIds | array | – | Optional selected source row ids. Omit only for the whole sheet. |
| sheetId | string | yes | Source company sheet UUID. |
| targetProfile | string | yes | Required target: owners for CNPJ owners/partners, or a functional leadership profile. |
No output schema declared.
No examples provided.
disqualify_prospect Desqualificar pessoa ~66
Take ONE person out: scope "campaign" removes them from this campaign's cadence; scope "list" also removes them from the people sheet they came from. Unsent steps stop.
| Name | Type | Req | Description |
|---|---|---|---|
| prospectId | string | yes | Exact prospect UUID. |
| scope | string | – | – |
No output schema declared.
No examples provided.
duplicate_sheet Duplicar planilha ~37
Copy one owned sheet, rows and columns, under a new name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| sheetId | string | yes | – |
No output schema declared.
No examples provided.
edit_sheet Editar planilha ~138
Edits a sheet the user owns with the same persistent operations as the dashboard: add custom/AI columns, rename/delete/hide/show/reorder/resize columns, update cells, or delete rows. Takes exact row and column ids.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| aiKind | string | – | – |
| cells | array | – | – |
| columnId | string | – | – |
| columnIds | array | – | – |
| columnType | string | – | – |
| instruction | string | – | – |
| name | string | – | – |
| rowIds | array | – | – |
| sheetId | string | yes | – |
| width | integer | – | – |
No output schema declared.
No examples provided.
enrich_field Enriquecer campo ~565
Enrich ONE specific sheet field for one person/company row. Uses the same field catalogue and provider cascade as the dashboard, stops as soon as that field is found, and returns found/not_found/error deterministically. Valid field ids and their inputs come from the enrichment field catalogue. First it looks the lead up in this workspace (people sheets, campaigns and kept briefs, by email, LinkedIn, or full name with the company): a value already saved comes back free, with savedIn naming the place it was saved. Only a found value is charged: creditsCharged is what this call cost, 0 when nothing was found, the lookup failed or the value was already saved. not_found with sourcesUnanswered means the sources that answered had nothing but that many others did not answer in time, so a later retry may find it; error means no source answered at all. Every result names the person it was looked up for (person: name, LinkedIn, company), so parallel calls are told apart by person, not by order. A mobile is checked against the registry's owner of the number before it is kept: phoneOwner is confirmed (the owner has the person's name) or unconfirmed (the registry has no name for it); a number of someone else is dropped and not charged (phonesDiscarded counts them). A mobile found for a person of this workspace's campaigns or people sheets is saved there (prospectId, or sheetId and rowId, identify the person; the LinkedIn profile also matches): savedTo says where.
| Name | Type | Req | Description |
|---|---|---|---|
| cnpj | string | – | Brazilian company registry number. |
| companyDomain | string | – | – |
| companyName | string | – | – |
| string | – | – | |
| fieldId | string | yes | Field id from the enrichment field catalogue, e.g. "work_email". |
| fullName | string | – | – |
| linkedinUrl | string | – | – |
| location | string | – | Person location hint used to reject off-country phones. |
| personalEmail | string | – | Personal/webmail address used by phone finders. |
| phone | string | – | – |
| prospectId | string | – | The campaign prospect this lookup is for, when known: a mobile found is saved to them. |
| providerOrder | array | – | Optional exact provider cascade. Every name must belong to the selected field. Omit it to use the field's configured cost-conscious order. |
| refresh | boolean | – | True skips what this workspace has saved and looks the value up outside again. |
| rowId | string | – | The sheet row this lookup is for, with sheetId: a mobile found is saved to its phone column. |
| sheetId | string | – | The people sheet of the row this lookup is for, with rowId. |
No output schema declared.
No examples provided.
enrich_field_batch Enriquecer campo de várias pessoas ~349
Enrich ONE field for up to 25 people in one call: the same lookup as the single-person enrichment for each person, run on Nock's side 5 at a time, so a list does not wait for one person after another (a mobile can take over a minute a person, so 10 mobiles take about 2 to 3 minutes and 25 about 6). results has one entry per person, in the order sent (index), each with the same fields as the single-person enrichment: person (whose it is), status found/not_found/error, value, phoneOwner, phonesDiscarded, creditsCharged, savedIn, savedTo, sourcesUnanswered (not_found while some sources did not answer in time: that person may be tried again later; error only when no source answered). Each value belongs to the person named in its entry. Only found values are charged, each at the field's price; creditsCharged at the top is the sum. The same person sent twice is looked up once (sameAsIndex, creditsCharged 0).
| Name | Type | Req | Description |
|---|---|---|---|
| fieldId | string | yes | Enrichment field id, e.g. "work_email". |
| people | array | yes | The people to look up, each with the same inputs as a single-person enrichment (name, company, LinkedIn, e-mail, prospectId or sheetId and rowId...). |
| providerOrder | array | – | Optional exact provider cascade. Every name must belong to the selected field. Omit it to use the field's configured cost-conscious order. |
| refresh | boolean | – | Only for an explicit request to look it up outside again: skips what this workspace has saved. |
No output schema declared.
No examples provided.
explore_signals Buscar sinais ~1,862
Search a buying signal like the Sinais screen: companies hiring a role (hiring), recent funding rounds (funding: periodDays 7/30/90/180), company news (news), companies showing a technology (tech), Brazilian company registry events (cnpj), companies that started a construction (construction), closed-lost CRM deals (crm) or people new in a role (job_change: jobTitle, periodDays 30/60/90, location, industry, companySizes; domains narrows to the user's accounts for "decisor novo na conta"; move new_company or promotion; each result is a person with the company they joined, the title and the month), companies whose team grew (growth: minGrowthPct, months 6 or 12, location, industry, companySizes; only companies with a LinkedIn page) or companies running ads now (ads: query, a theme in the advertisers' words, read in Meta's Ad Library in Brazil; or domains, up to 10 of the user's accounts checked on Google's Ads Transparency Center). cnpj.event picks what happened: opening (new CNPJ, the default), branch (opened a branch), mei_exit (left the MEI; stayedInSimples = became an ME), simples_exit (left the Simples Nacional), new_partner (a partner joined the QSA), gov_contract (signed a public contract, PNCP), debt_new (new federal active debt, PGFN), and from the Receita edition comparison capital_up, address_change, cnae_change. Every event but opening needs location with a state ("Curitiba, PR", "SC") or industry. construction is "Iniciou uma construção": companies that registered a construction project at the Receita's CNO; location with a state is required, minAreaM2 is optional, periodDays 7/30/90; cite Receita Federal (CNO). Each result's title already states the fact with its date, and facts.sourceProvider names its public source. Up to 200 results per search, set by limit (without it: 2 for hiring, funding, news, tech, cnpj and construction, 10 for the others). Charged per result returned: 4 credits each (8 for a hiring company found by the wider job-board search),…
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | – | true after the user agreed to a quote this tool returned. A search whose maximum is above max(50, 20% of the balance) credits runs only with it. |
| search | – | yes | – |
No output schema declared.
No examples provided.
export_sheet_csv Exportar planilha em CSV ~116
Export an owned enrichment sheet to deterministic UTF-8 CSV in its visible column order, one line per sheet row (a company's columns repeat on each of its people). perCompany: one line per company instead (the list of accounts), with how many of its people the sheet has and the first one. In the dashboard the returned CSV is downloaded automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| perCompany | boolean | – | One line per company (Pessoas na planilha, Primeiro decisor) instead of one per row. |
| sheetId | string | yes | – |
No output schema declared.
No examples provided.
export_signal_events Salvar eventos na planilha ~57
Save events of one monitor, by their event ids, into a company or people sheet. Repeated events are skipped.
| Name | Type | Req | Description |
|---|---|---|---|
| eventIds | array | yes | – |
| monitorId | string | yes | – |
| sheetId | string | yes | – |
No output schema declared.
No examples provided.
feed_campaign_with_signal Alimentar campanha com um sinal ~301
Make a campaign take, every day, the companies a signal monitor finds (including a custom signal monitor, market.category "custom"). The person at each company is the jobTitle given (or the campaign's); a social monitor (engagement with posts) gives the people themselves, no jobTitle. Linking is free; each person is charged as any campaign person when they enter. From then on the campaign enrolls people from the signal on its own, every day, and the signal delivers into the campaign's one sheet (what it delivered to a sheet of its own is copied in). Takes the exact campaign id; it does not pick a campaign by itself.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | The campaign that will take the signal's companies every day. |
| confirmed | boolean | – | true only after the user agreed to the monthly cost a quote returned. |
| enroll | string | – | all: the companies already found enter too; future: only the next ones. |
| jobTitle | string | – | Who to reach at each company, e.g. "Sócio, Proprietário, Diretor". |
| monitorId | string | yes | The signal (monitor) whose companies feed the campaign. |
| 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.
find_companies_using_erp Buscar empresas que usam um ERP ~2,986
Finds companies that run one of the ERPs asked (totvs, sap_business_one, sap, omie, sankhya, senior, linx, netsuite, dynamics, bling, tiny, contaazul, egestor, vhsys, marketup, gestaoclick, nomus), each proved with public evidence: a job post the company itself published, its site or its domain's e-mail setup. The same search, company check and filters as the "Usa ERP" signal (recruiters, accounting offices, ERP vendors and consultancies, and posts published for another company are left out), as a one-off list instead of a daily feed. Candidates come from job posts that name the ERP: Nock's job index (LinkedIn read every 6 hours, Gupy, Indeed, Vagas.com, Glassdoor, Sólides and others; a post whose employer has no site in the index is read too and the company found by name and place), LinkedIn searched live in the same call (one search per ERP asked with the area's words, and a second round while there is time and spend left), people in Brazil whose current job's title or description names the ERP (TOTVS/Protheus, Sankhya and SAP Business One; ERP vendors, IT consultancies and, per ERP, recruiters and accounting firms left out; one person per company, each company proved by that person's profile, never by the search alone; sources and routes name it "Pessoas que citam o ERP no cargo"), then openings in an area that runs it (hiringArea: fiscal_contabil by default, fiscal, contabil, controladoria, financeiro, compras), then companies of the market (location, industry, companySizes). Filters on the job post that brought the company, read BEFORE any check (a candidate that fails them is never checked nor charged): postedWithinDays (1 to 180, only posts published within that many days; a company with no dated post is left out) and jobPostTitles (words or titles, e.g. ["analista", "coordenador", "controller"], accents and case aside; a title of several words needs each). An ask that pairs the ERP with a job post in an area always maps to these filters: "usam TOTVS e abrir…
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Optional: only decision makers of this area. "financeiro" keeps finance people (CFO, finance director or manager, a finance controller) and leaves out other areas' titles such as "Controller Jurídico… |
| companies | array | – | Check a list the user already has instead of searching (50 at most): each company by name, domain or CNPJ. Each one comes back in list[] with its status (entregue, erp_nao_provado, prova_fraca, fora_… |
| companiesSheetId | string | – | Check the companies of this sheet instead (its name, site and CNPJ columns), the first 50. |
| companySizes | array | – | Headcount bands, e.g. ["51,200", "201,500"]. |
| confirmed | boolean | – | false or absent: returns the most it can cost and runs nothing. true: runs and charges. |
| decisionMakerFallback | string | – | When nobody holds the role asked (the finance titles by default): role_only, the default, leaves the company without a decision maker and says so (decisionMakerNotFound); partner accepts who decides… |
| erps | array | yes | Any of these ERPs (totvs, sap_business_one, sap, omie, sankhya, senior, linx, netsuite, dynamics, bling, tiny, contaazul, egestor, vhsys, marketup, gestaoclick, nomus); sap_business_one needs evidenc… |
| findPeople | boolean | – | false brings only the companies, no decision maker. Default true. |
| hiringArea | string | – | The area of the job post the user asks for: fiscal, contabil, controladoria, financeiro or compras (fiscal_contabil is the default search when none is asked). Pass it whenever the ask names an area (… |
| includeWeakProof | boolean | – | true also delivers companies whose only proof is a post that accepts other ERPs ("Winthor ou similares"), graded fraca. Default false: left out. An employee's profile is never fraca: it is proof (méd… |
| industry | string | – | The sector in plain words, e.g. "indústria de alimentos". |
| jobPostTitles | array | – | Optional: only companies whose job post's title has one of these words or titles, accents and case aside, e.g. ["analista", "coordenador", "controller"] (a title of several words needs each of them).… |
| jobTitle | string | – | Who to find at each company, titles tried in order, comma-separated. Default: the finance decision makers ("CFO, Diretor Financeiro, Gerente Financeiro, Controller, Controller Financeiro, Head de Fin… |
| limit | integer | – | Companies to bring, 10 by default, 200 at most. |
| location | string | – | A state or city, e.g. "SP" or "Curitiba, PR". Brazil when left out. |
| postedWithinDays | integer | – | Optional, 1 to 180: only companies whose job post was published within this many days ("abriram vaga nos últimos 30 dias" is 30). Applied before any check: an older post, or a company with no dated p… |
| sheetId | string | – | An existing sheet to add the companies to; companies already in it are skipped. Without it, a new sheet is made. |
| sheetName | string | – | The name of the sheet to use or make when there is no sheetId (a sheet of that name is reused). |
| withEmail | boolean | – | Also look up each decision maker's work e-mail. Default false. |
No output schema declared.
No examples provided.
find_companies_with_rules Buscar empresas com regras verificadas ~631
Find companies that meet very specific rules, checked one by one with evidence: e.g. "revendas de peças agrícolas no RS" (source: web search "revenda de peças agrícolas" in RS cities, or the Receita by CNAE 4661300; rules: "vende peças agrícolas, não só máquinas", "é revenda, não fabricante"). Each company's own site (or a web search on it) is read and every rule is judged as met, not met or no evidence. Every verified row costs 2 credits, passed or not; a sample is 20 rows by default (30 at most). Returns the funnel (verified, passed, which rule removed the most, credits per company that passed), the companies that passed with each rule's reason and evidence, and a new company sheet with every row and verdict. Sources: the Receita (registry) for an activity the CNAE names; Google Maps (maps: query and cities with the state) for local and small businesses, shops, clinics, resellers; the web when the trait is how the company describes itself; a company sheet the user already has. Manufacturers or brand owners of a kind of product ("fabricantes de bebidas, cosméticos, pet food") come from the Receita by the manufacturing CNAEs; a web search for them returns articles, associations and fairs about the theme. A rule about the CNAE or the Receita is checked against the company's registration, found from its CNPJ, site or exact name. Each rule is one short sentence, 300 characters at most, with one condition. Rules filter: a company missing one is out. A hot signal that makes a company better but not wrong (a recent launch, an ESG or recycling initiative, a hiring, growth) belongs in rankBy, not in rules: it orders the companies that passed, in the same read, at no extra cost. Not meant for a list the user already gave when nothing in it is to be filtered out ("nenhum critério é eliminatório", enrich, score or fill a table about each company). A rule about running ads (on Meta or Google), the Google rating, the Reclame Aqui reputation, site traffic or having an app is che…
| Name | Type | Req | Description |
|---|---|---|---|
| rankBy | array | – | Up to three signals that order the companies that passed and never remove one, e.g. "lançou produto nos últimos 6 meses", "tem iniciativa de reciclagem ou ESG". Checked in the same read, at no extra… |
| rules | array | yes | One to three rules each company must meet, in plain words, e.g. "vende peças agrícolas no site". |
| sample | integer | – | Rows to verify (default 20, at most 30). |
| source | – | yes | – |
No output schema declared.
No examples provided.
find_companies_with_signal Buscar empresas com um sinal agora ~1,569
Finds, now, companies of a market that show a buying signal, with one decision maker at each, and saves them in a sheet before it returns: a signal's daily monitor as a one-off list, with the same search, checks, kept answers and prices. category is the signal: hiring (open job posts: Nock's job index first, then the job boards; market.hiringTitle is the role), funding (rounds raised, each confirmed by a second source before it is delivered), news (news about the company: a kind of news or what happened, in the Brazilian press), job_change (people new in a role, at a new company or promoted: the person found is the decision maker, no lookup), erp (companies that run an ERP, proved with public evidence), cnpj (from the Receita through the Nock Registry: event opening = empresa nova, branch = filial nova, by industry or CNAE, place and periodDays 7/30/45/60/90; every event but opening needs a state or an industry; a branch has a CNPJ and no site), site_tech (tools the company's own site and e-mail domain load, e.g. HubSpot, RD Station: technologies and change uses, adopted or removed), tech (one tool by name; a tool the site shows, asked as presence, is read on the site as site_tech; any other comes from job posts and detections) and loyalty_club (supermarkets, by their main CNAE, checked for a loyalty club: filter sem_clube or clube_concorrente, location a state or a city). market takes the same fields as that signal's monitor (tech: technology, detectionMode, periodDays, location; online stores by their platform are not searched here). rules (hiring, news, cnpj) keep only the companies that meet them, each row checked charged. It also looks up one decision maker at each company (jobTitle, default "CEO, Sócio, Diretor"; area "financeiro" keeps only finance decision makers; decisionMakerFallback role_only, the default when jobTitle or area is given, leaves a company where nobody holds the role without one and says so (decisionMakerNotFound), partner accepts the Recei…
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Optional: only decision makers of this area ("financeiro" keeps finance people and leaves out titles such as "Controller Jurídico"); without jobTitle it also looks for the area's titles. |
| category | string | yes | The signal: hiring, funding, news, job_change, erp, cnpj, tech, site_tech, loyalty_club (and any other the description lists). |
| confirmed | boolean | – | false or absent: returns the most it can cost and runs nothing. true: runs and charges. |
| decisionMakerFallback | string | – | When nobody holds the role asked: role_only (the default when jobTitle or area is given) leaves the company without a decision maker and says so; partner accepts who decides there (the managing partn… |
| findPeople | boolean | – | false brings only the companies, no decision maker. Default true. |
| jobTitle | string | – | Who to find at each company, titles tried in order, comma-separated. Default "CEO, Sócio, Diretor". |
| limit | integer | – | Companies to bring, 10 by default, 200 at most. |
| market | object | yes | The market of that signal, with the same fields as that signal's monitor market (category may be left out). hiring: hiringTitle (required), location, seniority, companySizes, industry, rules; funding… |
| sheetId | string | – | An existing sheet to add the companies to; companies already in it are skipped and not charged. Without it, a new sheet is made. |
| sheetName | string | – | The name of the sheet to use or make when there is no sheetId (a sheet of that name is reused). |
| withEmail | boolean | – | Also look up each decision maker's work e-mail. Default false. |
No output schema declared.
No examples provided.
find_lead Encontrar lead no workspace ~106
Where a lead already is in this workspace and what is known about them: the people sheets whose rows match (with that row's fields, which may already hold the answer without enriching), the campaigns they are in and the briefs already made about them (who they are, title, LinkedIn, company). Pass an email, a LinkedIn URL, a name or a company. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Email, LinkedIn URL, name or company of the lead. |
No output schema declared.
No examples provided.
find_people_for_campaign Encontrar mais pessoas para a campanha ~294
Finds NEW people for an existing campaign now and adds them to it ("add 40 more people to this campaign"), from the campaign's saved search or its signal, the same search its daily additions run. People already in the campaign are skipped; each person found goes into the cadence and the campaign's sheet. At most 200 per call; a campaign has no size limit. It spends credits, so it works in two calls: the first, with confirmed false, returns the price per person and the most it can cost and adds nobody; a call with confirmed true finds and adds the people. status no_audience means the campaign has neither a saved search nor a signal. When the campaign's signal has nothing new, the confirmed call runs the signal now and waits up to two minutes for it. When fewer people came in than asked, the result's note explains why, and funnel and funnelText count who was found and why the rest did not enter (same company, no channel, already in the campaign, outside the profile, the signal, the balance); people who did not enter are not charged. It only finds new people; it does not add people already in a sheet.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | Exact campaign UUID. |
| confirmed | boolean | yes | false to get the price; true only after the user agreed to it. |
| count | integer | yes | How many new people to add. |
No output schema declared.
No examples provided.
forget_memory Esquecer memória do Nock Agent ~43
Forget saved memories of the workspace ("esquece isso"), by their memory ids as the knowledge base lists them. They are removed.
| Name | Type | Req | Description |
|---|---|---|---|
| memoryIds | array | yes | – |
No output schema declared.
No examples provided.
generate_outreach_campaign Criar campanha a partir de planilha ~724
Create a new outreach campaign from an existing sheet (sheetId is required). It drafts name, offering, goal, CTA and cadence from the workspace profile plus the instruction and attaches people from that people sheet after the draft (rowIds left out means every row, up to 1000). The sheet is only the audience list unless useSheetContext is true (a list of founders does not turn the campaign into a founder campaign); a campaign from a sheet claims no buying signal the request did not state, and is named after the sheet. Its channels follow what the list can receive (LinkedIn connections have no e-mail: a LinkedIn-only campaign); channels sets them explicitly ("no LinkedIn" = ["linkedin"]). channels ["whatsapp"] makes a cadence of WhatsApp only (steps the seller sends from the phone, or WhatsApp automático where the workspace sends it), and only people with a mobile enter; on a company sheet its quote then includes each person's mobile (phoneLookup: the company's WhatsApp do decisor first, 6 credits, else the person's mobile, 20, each only when found). Suited to creating a campaign from an existing sheet or to offering a demo. A COMPANY sheet works the same as sheetId, with no separate decision-maker step: the same sheet becomes the campaign's people, the decision makers of each company take its place, each row keeping the company's columns; a company where nobody is found stays, marked, out of the campaign. For a company sheet the first call only quotes (status needs_confirmation, with maxCredits for the first batch of up to 25 people) and spends nothing; a call with acceptedCredits equal to that maxCredits runs it. The other companies are converted by the campaign itself, a few a day, once it is active. areasNote, when present, flags people who may not fit; they can come out of the list or stay with that version ("Tirar da lista" on the campaign's Template tab). templateId is not accepted.When people of the campaign still wait on their sheet row's e-mail, LinkedIn o…
| Name | Type | Req | Description |
|---|---|---|---|
| acceptedCredits | integer | – | Only for a company sheet, on the second call: the maxCredits the first call returned, after the user agreed. |
| channels | array | – | Channels the user asked for; ["whatsapp"] for WhatsApp only. Omit to use the ones the sheet's people can receive. |
| decisionMakers | object | – | Only for a company sheet: whom to write to at each company. Omit to use the account's persona. |
| instruction | string | – | What the campaign should sell or ask for, e.g. offer a Nock demo. |
| locale | string | – | Copy language. Defaults to Português (Brasil). |
| rowIds | array | – | Optional subset. Omit to attach every people row in the sheet. |
| sheetId | string | yes | Sheet UUID: a people sheet (its people) or a company sheet (its decision makers). |
| useSheetContext | boolean | – | When true, use roles/companies from the sheet to form the campaign targeting. Default false: the sheet is only the audience and must not change the campaign slice. |
| withSignalOnly | boolean | – | Only the rows of the companies whose rows show a buying signal in the sheet (its Sinal column), within rowIds when given. |
No output schema declared.
No examples provided.
get_credit_balance Saldo de créditos ~55
The workspace's credits now: how many are available to spend, how many are held by operations still running, and the plan. Answers how many credits the workspace has and whether an action fits the balance. Free and read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_customer_list Ler lista de clientes ~35
Read the workspace's customer list: companies that are already customers. Nobody at them gets a first message and searches leave them out.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_inbox_conversation Abrir conversa ~56
Read one Inbox conversation (every message both ways) with a campaign person on one channel.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
| prospectId | string | yes | prospectId of the conversation, as the Inbox list returns it. |
No output schema declared.
No examples provided.
get_knowledge_base Ler perfil da empresa ~50
Read the workspace's company profile (what it sells, ICP, persona, pains, competitors, exclusions), its documents, and what you learned in earlier conversations (memories, each with its id).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_prospect Detalhar prospecção ~78
Get ONE prospect owned by the authenticated user: the full LinkedIn connection note, the email subject and body, the captured sheet context, its owner ("Responsável", the member who sends its WhatsApp tasks, null for nobody) and the activity history (generation, edits, status changes).
| Name | Type | Req | Description |
|---|---|---|---|
| prospectId | string | yes | Exact prospect UUID. |
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.