Italian B2B Lead List Scoring, Ranking & JSON Decisions

Server Details

Prioritize an existing Italian B2B lead list into up to 250 explained JSON decisions.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 99.9% over 42 days
Last Tested: 2026-09-28 20:12
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4/5.0

Scored 2026-09-09 19:59 across 6 tools

Disambiguation5/5

Each tool targets a distinct aspect of the pre-sales and product information workflow: buyer qualification, catalog access, purchase prerequisites, synthetic previews, need mapping, and order preparation. There is no overlap in purpose, and the descriptions clearly delineate boundaries.

Naming Consistency5/5

All six tools follow a consistent verb_noun pattern in snake_case (check_, get_, map_, prepare_), with clear, descriptive verbs. The naming convention is uniform and predictable.

Tool Count5/5

With exactly 6 tools, the set is well-scoped for the stated purpose. Each tool contributes a distinct function, and the count falls within the ideal range for a focused server.

Completeness2/5

Despite the server's name suggesting scoring, ranking, and JSON decision generation, none of the tools actually perform these core operations. The set only covers pre-sales qualification, catalog access, and order preparation, leaving the primary functionality missing. Agents would require an external process to actually score or rank a lead list.

Available Tools

6 tools

check_buyer_fitCheck MachineSignal buyer fitA

Read-onlyIdempotent

Inspect

Check whether an Italian B2B buyer with an existing company, domain, CRM or lead list can use MS-DEC-250 to score, rank and prioritize up to 250 records. Coarse non-personal facts only; it creates no order.

ParametersJSON Schema

Name	Required	Description
`country`	Yes	Two-letter country code, for example IT.
`primary_need`	No	Optional non-personal demand category used only in ephemeral aggregate counters; never send free text or buyer data.
`customer_type`	Yes	Buyer type. MachineSignal accepts B2B only.
`requested_product_code`	No	Product being considered. Defaults to the entry product MS-DEC-250.
`has_existing_company_list`	Yes	Whether the buyer already has a company, domain, CRM or lead list to evaluate.

Output Schema

ParametersJSON Schema

Name	Required	Description
`reason`	Yes
`eligible`	Yes
`boundaries`	Yes	Permanent safety boundaries of the public MCP discovery server.
`fit_status`	Yes
`reason_code`	Yes
`next_resource`	No
`ready_to_prepare`	Yes
`checkout_url_returned`	No
`recommended_next_tool`	No
`requested_product_code`	Yes
`recommended_next_arguments`	No
`next_step_after_preparation`	No
`buyer_data_must_remain_local`	Yes

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds 'Coarse non-personal facts only' and the warning in parameter descriptions about not sending free text or buyer data, which enriches the behavioral context. No contradictions found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description consists of two efficient sentences: the first captures the primary purpose and conditions, the second adds safety context. No superfluous words; every element earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (5 parameters, 3 enums, output schema exists but not shown), the description covers the key use case and behavioral constraints. It could be improved by explicitly noting that the country parameter should be 'IT' for Italian buyers, but the schema handles that implicitly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with good parameter descriptions. The tool description further clarifies how parameters interconnect (e.g., 'Italian' implies country='IT', 'B2B' ties to customer_type, 'existing company' ties to has_existing_company_list). This adds meaning beyond the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Check' and the specific resource (buyer fit for MS-DEC-250), along with key conditions (Italian, B2B, existing company list). It also implicitly distinguishes from sibling tools like prepare_order_intent by focusing on eligibility rather than order creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool (checking eligibility before order), but does not explicitly state when not to use it or mention alternatives. The directive 'it creates no order' hints at its safe, non-committal nature, but lacks explicit exclusionary guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_product_catalogGet MachineSignal product catalogA

Read-onlyIdempotent

Inspect

Find an API product to score, classify, rank and prioritize an existing Italian B2B company or lead list into up to 250 explained JSON decisions. Returns the canonical catalog and permanent safety boundaries; read-only and no buyer data.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`service`	Yes
`version`	Yes
`products`	Yes
`resources`	Yes	Canonical public MachineSignal resources.
`boundaries`	Yes	Permanent safety boundaries of the public MCP discovery server.

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive. The description adds context about permanent safety boundaries, no buyer data, and return of explained JSON decisions, which is valuable beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: first action-oriented, second adds safety context. No wasted words or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 0 parameters, comprehensive annotations, and an output schema (mentioned), the description provides enough context for the agent to select and invoke correctly, including constraints (Italian B2B, up to 250 decisions) and return type.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so schema coverage is 100%. Per guidelines, baseline is 4 for 0 params; description does not need to add parameter info.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns the 'MachineSignal product catalog' and its purpose for scoring/classifying/ranking B2B companies. It distinguishes itself from siblings by focusing on the catalog itself, though it does not explicitly contrast with tools like 'get_purchase_requirements'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use before other tools by saying 'Find an API product to score...', and notes it is read-only with no buyer data, suggesting safe usage. However, it lacks explicit guidance on when not to use this tool or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_purchase_requirementsGet controlled purchase requirementsA

Read-onlyIdempotent

Inspect

Explain the machine-origin purchase prerequisites without accepting an order, returning checkout data or calling a provider.

ParametersJSON Schema

Name	Required	Description	Default
`product_code`	Yes	Product whose controlled machine-origin purchase requirements should be returned.

Output Schema

ParametersJSON Schema

Name	Required	Description
`boundaries`	Yes	Permanent safety boundaries of the public MCP discovery server.
`order_policy`	Yes
`product_code`	Yes
`customer_scope`	Yes
`legal_resources`	Yes
`ready_to_prepare`	Yes
`input_requirement`	Yes
`machine_onboarding`	Yes
`checkout_url_returned`	Yes
`recommended_next_tool`	No
`mcp_order_tool_exposed`	Yes
`recommended_next_arguments`	No
`next_step_after_preparation`	No
`authoritative_order_protocol`	Yes
`buyer_data_must_remain_local`	Yes

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds extra transparency by explicitly stating that no order is accepted, no checkout data is returned, and no external provider is called. This aligns with annotations and provides further behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the main action and includes clarifying details. Every phrase earns its place with no waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (not needing return-value explanation), a single well-described parameter, and supportive annotations, the description covers all necessary aspects. It is complete for an informational tool with low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage with a clear description for the only parameter. The tool description does not add new information about the parameter beyond what the schema already provides, so it meets the baseline without extra contribution.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Explain' and the resource 'machine-origin purchase prerequisites'. It explicitly distinguishes itself from siblings by listing what it does NOT do (accept orders, return checkout data, or call a provider), making its purpose distinct.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly explains when to use the tool (to explain prerequisites) and clarifies that it is not for actual ordering. However, it does not explicitly contrast with sibling tools or state when to choose this over alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_synthetic_exampleGet a synthetic MachineSignal output exampleA

Read-onlyIdempotent

Inspect

Preview the JSON produced when MachineSignal scores, classifies, ranks and prioritizes an Italian B2B lead list. Uses approved synthetic data only and creates no order.

ParametersJSON Schema

Name	Required	Description	Default
`product_code`	Yes	Product whose approved synthetic output preview should be returned.

Output Schema

ParametersJSON Schema

Name	Required	Description
`example`	Yes	Approved synthetic product preview; never real buyer or company data.
`boundaries`	Yes	Permanent safety boundaries of the public MCP discovery server.
`canonical_example_url`	Yes

TDQS

A4.3/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context: 'Uses approved synthetic data only and creates no order'. This clarifies data source and confirms no side effects, going beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the main purpose. Every sentence adds value—no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one enum parameter and an output schema, the description is complete. It explains purpose, data source, and side effects. No need to describe return values since output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and includes a description for the single parameter. The tool description does not add additional meaning about the parameter beyond what the schema provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Preview' and the resource 'JSON produced when MachineSignal scores... an Italian B2B lead list'. It distinguishes from siblings which focus on checking fit, catalog, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for previewing synthetic output, but does not explicitly state when to use versus alternatives or when not to use. No sibling differentiation is mentioned in the description itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

map_business_needMap a general B2B business need for product researchA

Read-onlyIdempotent

Inspect

Map any structured B2B business need from Italy or a foreign market for aggregate product research. Italy remains the only commercial sales scope; foreign signals are research-only. The tool accepts only closed semantic fields and never creates a product or order.

ParametersJSON Schema

Name	Required	Description
`country`	No	Legacy 1.2.0 compatibility for Italian demand. Omit it when origin_market is supplied.
`urgency`	No	How soon the capability would be useful; defaults to exploratory.
`recurrence`	No	Whether the need is one-off, recurring or continuous; defaults to unknown.
`budget_band`	No	Optional coarse willingness-to-pay band in EUR; never send payment data.
`need_action`	Yes	Primary action the machine wants the capability to perform.
`need_domain`	Yes	Broad business domain of the requested capability; use other only when none applies.
`need_object`	Yes	Business object or subject on which the action should operate.
`customer_type`	Yes	Only business demand is observed; this does not expand commercial eligibility.
`origin_market`	No	Self-declared coarse origin bucket used only for aggregate research; defaults to UNKNOWN_NOT_DECLARED. Foreign buckets never enable sales.
`desired_output`	Yes	Machine-readable or operational result the buyer wants.
`existing_product_fit`	No	Whether an existing MachineSignal product appears to fit; defaults to unknown.

Output Schema

ParametersJSON Schema

Name	Required	Description
`scope`	Yes
`boundaries`	Yes	Permanent safety boundaries of the public MCP discovery server.
`signal_type`	Yes
`order_created`	Yes
`origin_market`	Yes
`persists_data`	Yes
`mapping_status`	Yes
`need_signature`	Yes
`product_created`	Yes
`free_text_accepted`	Yes
`buyer_data_accepted`	Yes
`market_verification`	Yes
`existing_product_fit`	Yes
`checkout_url_returned`	Yes
`potential_product_gap`	Yes
`provider_call_enabled`	Yes
`commercial_eligibility`	Yes

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate read-only, idempotent, non-destructive. Description adds key behaviors: never creates a product or order, and clarifies territorial scope for research vs commercial use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences front-load the core purpose, then add scope constraints. No unnecessary words, each sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 11 parameters, an output schema exists, and annotations cover safety, the description adequately adds key constraints (scope, non-creation). Could mention that mapping implies aggregate research only, but overall sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description ('accepts only closed semantic fields') adds minimal value beyond the schema's detailed enumerations and descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool maps structured B2B business needs for product research, with specific scopes (Italy or foreign). It distinguishes from siblings like prepare_order_intent by noting it never creates a product or order.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context on when to use (mapping needs for research) and when not (never creates products/orders), and limits commercial scope to Italy. Lacks explicit references to sibling tools but context is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

prepare_order_intentPrepare a local MS-DEC-250 order-intent templateA

Read-onlyIdempotent

Inspect

Return the canonical endpoint, OpenAPI, 17 required fields and a locally fillable MS-DEC-250 template. It accepts no buyer data and never creates an order.

ParametersJSON Schema

Name	Required	Description	Default
`product_code`	Yes	Entry product whose order-intent template should be prepared locally without submitting it.

Output Schema

ParametersJSON Schema

Name	Required	Description
`boundaries`	Yes	Permanent safety boundaries of the public MCP discovery server.
`instructions`	Yes
`product_code`	Yes
`order_created`	Yes
`order_openapi`	Yes
`persists_data`	Yes
`submit_method`	Yes
`order_endpoint`	Yes
`required_fields`	Yes
`accepts_buyer_data`	Yes
`idempotency_header`	Yes
`preparation_status`	Yes
`request_schema_ref`	Yes
`local_fill_template`	Yes
`static_order_openapi`	Yes
`checkout_url_returned`	Yes
`provider_call_enabled`	Yes
`validation_profile_url`	Yes

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds value beyond annotations (readOnlyHint, idempotentHint, destructiveHint) by stating 'It accepts no buyer data and never creates an order,' which provides key behavioral context not in annotations. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the most important information (what it returns), and no unnecessary words. Every sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no nested objects, good annotations, output schema exists), the description fully covers the tool's purpose, behavior, and limitations. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single parameter (product_code with const and description), so the description does not need to add parameter details. Baseline 3 is appropriate; no extra semantic value from description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that it returns a canonical endpoint, OpenAPI, required fields, and a fillable template for MS-DEC-250. It uses a specific verb 'return' and resource 'MS-DEC-250 order-intent template', distinguishing it from siblings like 'check_buyer_fit' which check fit, not prepare templates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'It accepts no buyer data and never creates an order', which guides when not to use it. However, it does not explicitly state when to use it or name alternatives, leaving room for clearer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updateJul 29, 2026

Changedget_product_catalog6 fields changed

addedOutput schema / properties / resources / properties / lead_opportunity_score_api_landing
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
addedOutput schema / properties / resources / properties / market_potential_analysis_api_guide_it
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
addedOutput schema / properties / resources / properties / official_mcp_registry_canonical
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
addedOutput schema / properties / resources / properties / official_mcp_registry_semantic_alias
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
addedOutput schema / properties / resources / properties / target_company_prioritization_guide_it
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```

changedOutput schema / properties / resources / required

Previous value: -[
-  "website",
-  "buyer_agent",
-  "product_catalog",
-  "agent_sales",
-  "machine_onboarding",
-  "openapi",
-  "llms",
-  "mcp_server_card",
-  "discovery",
-  "terms",
-  "privacy",
-  "refund",
-  "order_intent_validation_profile"
-]New value: +[
+  "website",
+  "buyer_agent",
+  "product_catalog",
+  "agent_sales",
+  "machine_onboarding",
+  "openapi",
+  "lead_opportunity_score_api_landing",
+  "target_company_prioritization_guide_it",
+  "market_potential_analysis_api_guide_it",
+  "llms",
+  "mcp_server_card",
+  "official_mcp_registry_canonical",
+  "official_mcp_registry_semantic_alias",
+  "discovery",
+  "terms",
+  "privacy",
+  "refund",
+  "order_intent_validation_profile"
+]

1 tool updateJul 22, 2026

Changedget_product_catalog3 fields changed

removedOutput schema / properties / resources / properties / agent_card
```
Removed value: -{
-  "format": "uri",
-  "type": "string"
-}
```
addedOutput schema / properties / resources / properties / mcp_server_card
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```

changedOutput schema / properties / resources / required

Previous value: -[
-  "website",
-  "buyer_agent",
-  "product_catalog",
-  "agent_sales",
-  "machine_onboarding",
-  "openapi",
-  "llms",
-  "agent_card",
-  "discovery",
-  "terms",
-  "privacy",
-  "refund",
-  "order_intent_validation_profile"
-]New value: +[
+  "website",
+  "buyer_agent",
+  "product_catalog",
+  "agent_sales",
+  "machine_onboarding",
+  "openapi",
+  "llms",
+  "mcp_server_card",
+  "discovery",
+  "terms",
+  "privacy",
+  "refund",
+  "order_intent_validation_profile"
+]

1 tool updateJul 22, 2026

Changedmap_business_need12 fields changed

changedInput schema / properties / country / description

Previous value: -"Commercial scope is limited to Italy."New value: +"Legacy 1.2.0 compatibility for Italian demand. Omit it when origin_market is supplied."

changedInput schema / properties / customer_type / description

Previous value: -"Only business buyers are in scope."New value: +"Only business demand is observed; this does not expand commercial eligibility."

addedInput schema / properties / origin_market

Added value: +{
+  "description": "Self-declared coarse origin bucket used only for aggregate research; defaults to UNKNOWN_NOT_DECLARED. Foreign buckets never enable sales.",
+  "enum": [
+    "IT",
+    "EU_NON_IT",
+    "EXTRA_EU",
+    "UNKNOWN_NOT_DECLARED"
+  ],
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "country",
-  "customer_type",
-  "need_domain",
-  "need_action",
-  "need_object",
-  "desired_output"
-]New value: +[
+  "customer_type",
+  "need_domain",
+  "need_action",
+  "need_object",
+  "desired_output"
+]

addedOutput schema / properties / commercial_eligibility

Added value: +{
+  "enum": [
+    "b2b_italy_sales_scope",
+    "research_only_not_commercially_eligible"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / market_verification

Added value: +{
+  "const": "structured_self_declared_bucket_not_identity_verified",
+  "type": "string"
+}

addedOutput schema / properties / need_signature / properties / origin_market

Added value: +{
+  "enum": [
+    "IT",
+    "EU_NON_IT",
+    "EXTRA_EU",
+    "UNKNOWN_NOT_DECLARED"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / need_signature / required

Previous value: -[
-  "domain",
-  "action",
-  "object",
-  "output",
-  "urgency",
-  "recurrence",
-  "budget_band"
-]New value: +[
+  "origin_market",
+  "domain",
+  "action",
+  "object",
+  "output",
+  "urgency",
+  "recurrence",
+  "budget_band"
+]

addedOutput schema / properties / origin_market

Added value: +{
+  "enum": [
+    "IT",
+    "EU_NON_IT",
+    "EXTRA_EU",
+    "UNKNOWN_NOT_DECLARED"
+  ],
+  "type": "string"
+}

removedOutput schema / properties / scope / const

Removed value: -"B2B_Italy_general_business_need"

addedOutput schema / properties / scope / enum

Added value: +[
+  "B2B_Italy_general_business_need",
+  "B2B_global_demand_research_sales_italy_only"
+]

changedOutput schema / required

Previous value: -[
-  "mapping_status",
-  "scope",
-  "need_signature",
-  "existing_product_fit",
-  "potential_product_gap",
-  "signal_type",
-  "free_text_accepted",
-  "buyer_data_accepted",
-  "persists_data",
-  "product_created",
-  "order_created",
-  "checkout_url_returned",
-  "provider_call_enabled",
-  "boundaries"
-]New value: +[
+  "mapping_status",
+  "scope",
+  "origin_market",
+  "market_verification",
+  "commercial_eligibility",
+  "need_signature",
+  "existing_product_fit",
+  "potential_product_gap",
+  "signal_type",
+  "free_text_accepted",
+  "buyer_data_accepted",
+  "persists_data",
+  "product_created",
+  "order_created",
+  "checkout_url_returned",
+  "provider_call_enabled",
+  "boundaries"
+]

1 tool updateJul 21, 2026
- Addedmap_business_need

4 tool updatesJul 21, 2026

Changedcheck_buyer_fit7 fields changed

addedInput schema / properties / primary_need

Added value: +{
+  "description": "Optional non-personal demand category used only in ephemeral aggregate counters; never send free text or buyer data.",
+  "enum": [
+    "score_existing_company_list",
+    "discover_target_companies",
+    "prioritize_leads",
+    "market_potential_analysis",
+    "deep_company_analysis",
+    "build_actionable_campaign",
+    "crm_workflow_automation",
+    "monitor_market_changes",
+    "competitor_analysis",
+    "other_structured_b2b_need"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / buyer_data_must_remain_local
```
Added value: +{
+  "const": true,
+  "type": "boolean"
+}
```
addedOutput schema / properties / next_step_after_preparation
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / ready_to_prepare
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / recommended_next_arguments

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "product_code": {
+      "const": "MS-DEC-250",
+      "type": "string"
+    }
+  },
+  "required": [
+    "product_code"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / recommended_next_tool

Added value: +{
+  "const": "prepare_order_intent",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "fit_status",
-  "eligible",
-  "requested_product_code",
-  "reason_code",
-  "reason",
-  "boundaries"
-]New value: +[
+  "fit_status",
+  "eligible",
+  "requested_product_code",
+  "reason_code",
+  "reason",
+  "ready_to_prepare",
+  "buyer_data_must_remain_local",
+  "boundaries"
+]

Changedget_product_catalog2 fields changed

addedOutput schema / properties / resources / properties / order_intent_validation_profile
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```

changedOutput schema / properties / resources / required

Previous value: -[
-  "website",
-  "buyer_agent",
-  "product_catalog",
-  "agent_sales",
-  "machine_onboarding",
-  "openapi",
-  "llms",
-  "agent_card",
-  "discovery",
-  "terms",
-  "privacy",
-  "refund"
-]New value: +[
+  "website",
+  "buyer_agent",
+  "product_catalog",
+  "agent_sales",
+  "machine_onboarding",
+  "openapi",
+  "llms",
+  "agent_card",
+  "discovery",
+  "terms",
+  "privacy",
+  "refund",
+  "order_intent_validation_profile"
+]

Changedget_purchase_requirements6 fields changed

addedOutput schema / properties / buyer_data_must_remain_local
```
Added value: +{
+  "const": true,
+  "type": "boolean"
+}
```
addedOutput schema / properties / next_step_after_preparation
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / ready_to_prepare
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / recommended_next_arguments

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "product_code": {
+      "const": "MS-DEC-250",
+      "type": "string"
+    }
+  },
+  "required": [
+    "product_code"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / recommended_next_tool

Added value: +{
+  "const": "prepare_order_intent",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "product_code",
-  "customer_scope",
-  "input_requirement",
-  "order_policy",
-  "authoritative_order_protocol",
-  "machine_onboarding",
-  "legal_resources",
-  "mcp_order_tool_exposed",
-  "checkout_url_returned",
-  "boundaries"
-]New value: +[
+  "product_code",
+  "customer_scope",
+  "input_requirement",
+  "order_policy",
+  "authoritative_order_protocol",
+  "machine_onboarding",
+  "legal_resources",
+  "ready_to_prepare",
+  "buyer_data_must_remain_local",
+  "mcp_order_tool_exposed",
+  "checkout_url_returned",
+  "boundaries"
+]

Changedprepare_order_intent2 fields changed

addedOutput schema / properties / validation_profile_url

Added value: +{
+  "format": "uri",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "preparation_status",
-  "product_code",
-  "submit_method",
-  "order_endpoint",
-  "order_openapi",
-  "static_order_openapi",
-  "request_schema_ref",
-  "idempotency_header",
-  "required_fields",
-  "local_fill_template",
-  "instructions",
-  "accepts_buyer_data",
-  "persists_data",
-  "order_created",
-  "checkout_url_returned",
-  "provider_call_enabled",
-  "boundaries"
-]New value: +[
+  "preparation_status",
+  "product_code",
+  "submit_method",
+  "order_endpoint",
+  "order_openapi",
+  "static_order_openapi",
+  "request_schema_ref",
+  "validation_profile_url",
+  "idempotency_header",
+  "required_fields",
+  "local_fill_template",
+  "instructions",
+  "accepts_buyer_data",
+  "persists_data",
+  "order_created",
+  "checkout_url_returned",
+  "provider_call_enabled",
+  "boundaries"
+]

1 tool updateJul 21, 2026
- Addedprepare_order_intent

4 tool updatesJul 21, 2026

Changedcheck_buyer_fit4 fields changed

addedInput schema / properties / customer_type / description

Added value: +"Buyer type. MachineSignal accepts B2B only."

addedInput schema / properties / has_existing_company_list / description

Added value: +"Whether the buyer already has a company, domain, CRM or lead list to evaluate."

addedInput schema / properties / requested_product_code / description

Added value: +"Product being considered. Defaults to the entry product MS-DEC-250."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "boundaries": {
+      "additionalProperties": false,
+      "description": "Permanent safety boundaries of the public MCP discovery server.",
+      "properties": {
+        "accepts_buyer_data": {
+          "const": false,
+          "type": "boolean"
+        },
+        "b2b_italy_only": {
+          "const": true,
+          "description": "Only Italian B2B buyers are in commercial scope.",
+          "type": "boolean"
+        },
+        "checkout_url_exposed": {
+          "const": false,
+          "type": "boolean"
+        },
+        "external_outreach_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "invoice_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "marketplace_publication_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "mode": {
+          "const": "public_read_only_discovery",
+          "description": "Public discovery mode; never an order-processing surface.",
+          "type": "string"
+        },
+        "order_tool_exposed": {
+          "const": false,
+          "type": "boolean"
+        },
+        "payment_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "persists_data": {
+          "const": false,
+          "type": "boolean"
+        },
+        "provider_call_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "provider_reference_loaded": {
+          "const": false,
+          "type": "boolean"
+        },
+        "sdi_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "wise_payout_enabled": {
+          "const": false,
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "mode",
+        "b2b_italy_only",
+        "accepts_buyer_data",
+        "persists_data",
+        "order_tool_exposed",
+        "checkout_url_exposed",
+        "provider_reference_loaded",
+        "provider_call_enabled",
+        "payment_enabled",
+        "invoice_enabled",
+        "sdi_enabled",
+        "wise_payout_enabled",
+        "external_outreach_enabled",
+        "marketplace_publication_enabled"
+      ],
+      "type": "object"
+    },
+    "checkout_url_returned": {
+      "const": false,
+      "type": "boolean"
+    },
+    "eligible": {
+      "type": "boolean"
+    },
+    "fit_status": {
+      "enum": [
+        "blocked",
+        "not_fit",
+        "continuation_entitlement_required",
+        "fit_for_controlled_dec_order_intent"
+      ],
+      "type": "string"
+    },
+    "next_resource": {
+      "format": "uri",
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "reason_code": {
+      "type": "string"
+    },
+    "requested_product_code": {
+      "enum": [
+        "MS-DEC-250",
+        "MS-ACT-25"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "fit_status",
+    "eligible",
+    "requested_product_code",
+    "reason_code",
+    "reason",
+    "boundaries"
+  ],
+  "type": "object"
+}

Changedget_product_catalog1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "boundaries": {
+      "additionalProperties": false,
+      "description": "Permanent safety boundaries of the public MCP discovery server.",
+      "properties": {
+        "accepts_buyer_data": {
+          "const": false,
+          "type": "boolean"
+        },
+        "b2b_italy_only": {
+          "const": true,
+          "description": "Only Italian B2B buyers are in commercial scope.",
+          "type": "boolean"
+        },
+        "checkout_url_exposed": {
+          "const": false,
+          "type": "boolean"
+        },
+        "external_outreach_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "invoice_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "marketplace_publication_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "mode": {
+          "const": "public_read_only_discovery",
+          "description": "Public discovery mode; never an order-processing surface.",
+          "type": "string"
+        },
+        "order_tool_exposed": {
+          "const": false,
+          "type": "boolean"
+        },
+        "payment_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "persists_data": {
+          "const": false,
+          "type": "boolean"
+        },
+        "provider_call_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "provider_reference_loaded": {
+          "const": false,
+          "type": "boolean"
+        },
+        "sdi_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "wise_payout_enabled": {
+          "const": false,
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "mode",
+        "b2b_italy_only",
+        "accepts_buyer_data",
+        "persists_data",
+        "order_tool_exposed",
+        "checkout_url_exposed",
+        "provider_reference_loaded",
+        "provider_call_enabled",
+        "payment_enabled",
+        "invoice_enabled",
+        "sdi_enabled",
+        "wise_payout_enabled",
+        "external_outreach_enabled",
+        "marketplace_publication_enabled"
+      ],
+      "type": "object"
+    },
+    "products": {
+      "items": {
+        "additionalProperties": true,
+        "description": "Canonical product summary; product-specific output lists may also be present.",
+        "properties": {
+          "customer_scope": {
+            "type": "string"
+          },
+          "delivery_unit": {
+            "type": "string"
+          },
+          "example_url": {
+            "format": "uri",
+            "type": "string"
+          },
+          "input_requirement": {
+            "type": "string"
+          },
+          "order_policy": {
+            "type": "string"
+          },
+          "price_eur": {
+            "minimum": 0,
+            "type": "number"
+          },
+          "product_code": {
+            "enum": [
+              "MS-DEC-250",
+              "MS-ACT-25"
+            ],
+            "type": "string"
+          },
+          "product_name": {
+            "type": "string"
+          },
+          "product_page": {
+            "format": "uri",
+            "type": "string"
+          },
+          "public_checkout": {
+            "const": false,
+            "type": "boolean"
+          },
+          "role": {
+            "enum": [
+              "entry_product",
+              "post_dec_continuation"
+            ],
+            "type": "string"
+          },
+          "stamp_duty_eur": {
+            "minimum": 0,
+            "type": "number"
+          },
+          "total_due_eur": {
+            "minimum": 0,
+            "type": "number"
+          }
+        },
+        "required": [
+          "product_code",
+          "product_name",
+          "role",
+          "price_eur",
+          "stamp_duty_eur",
+          "total_due_eur",
+          "customer_scope",
+          "input_requirement",
+          "delivery_unit",
+          "example_url",
+          "product_page",
+          "order_policy",
+          "public_checkout"
+        ],
+        "type": "object"
+      },
+      "maxItems": 2,
+      "minItems": 2,
+      "type": "array"
+    },
+    "resources": {
+      "additionalProperties": false,
+      "description": "Canonical public MachineSignal resources.",
+      "properties": {
+        "agent_card": {
+          "format": "uri",
+          "type": "string"
+        },
+        "agent_sales": {
+          "format": "uri",
+          "type": "string"
+        },
+        "buyer_agent": {
+          "format": "uri",
+          "type": "string"
+        },
+        "discovery": {
+          "format": "uri",
+          "type": "string"
+        },
+        "llms": {
+          "format": "uri",
+          "type": "string"
+        },
+        "machine_onboarding": {
+          "format": "uri",
+          "type": "string"
+        },
+        "openapi": {
+          "format": "uri",
+          "type": "string"
+        },
+        "privacy": {
+          "format": "uri",
+          "type": "string"
+        },
+        "product_catalog": {
+          "format": "uri",
+          "type": "string"
+        },
+        "refund": {
+          "format": "uri",
+          "type": "string"
+        },
+        "terms": {
+          "format": "uri",
+          "type": "string"
+        },
+        "website": {
+          "format": "uri",
+          "type": "string"
+        }
+      },
+      "required": [
+        "website",
+        "buyer_agent",
+        "product_catalog",
+        "agent_sales",
+        "machine_onboarding",
+        "openapi",
+        "llms",
+        "agent_card",
+        "discovery",
+        "terms",
+        "privacy",
+        "refund"
+      ],
+      "type": "object"
+    },
+    "service": {
+      "const": "MachineSignal",
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "service",
+    "version",
+    "products",
+    "resources",
+    "boundaries"
+  ],
+  "type": "object"
+}

Changedget_purchase_requirements2 fields changed

addedInput schema / properties / product_code / description

Added value: +"Product whose controlled machine-origin purchase requirements should be returned."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "authoritative_order_protocol": {
+      "format": "uri",
+      "type": "string"
+    },
+    "boundaries": {
+      "additionalProperties": false,
+      "description": "Permanent safety boundaries of the public MCP discovery server.",
+      "properties": {
+        "accepts_buyer_data": {
+          "const": false,
+          "type": "boolean"
+        },
+        "b2b_italy_only": {
+          "const": true,
+          "description": "Only Italian B2B buyers are in commercial scope.",
+          "type": "boolean"
+        },
+        "checkout_url_exposed": {
+          "const": false,
+          "type": "boolean"
+        },
+        "external_outreach_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "invoice_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "marketplace_publication_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "mode": {
+          "const": "public_read_only_discovery",
+          "description": "Public discovery mode; never an order-processing surface.",
+          "type": "string"
+        },
+        "order_tool_exposed": {
+          "const": false,
+          "type": "boolean"
+        },
+        "payment_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "persists_data": {
+          "const": false,
+          "type": "boolean"
+        },
+        "provider_call_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "provider_reference_loaded": {
+          "const": false,
+          "type": "boolean"
+        },
+        "sdi_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "wise_payout_enabled": {
+          "const": false,
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "mode",
+        "b2b_italy_only",
+        "accepts_buyer_data",
+        "persists_data",
+        "order_tool_exposed",
+        "checkout_url_exposed",
+        "provider_reference_loaded",
+        "provider_call_enabled",
+        "payment_enabled",
+        "invoice_enabled",
+        "sdi_enabled",
+        "wise_payout_enabled",
+        "external_outreach_enabled",
+        "marketplace_publication_enabled"
+      ],
+      "type": "object"
+    },
+    "checkout_url_returned": {
+      "const": false,
+      "type": "boolean"
+    },
+    "customer_scope": {
+      "type": "string"
+    },
+    "input_requirement": {
+      "type": "string"
+    },
+    "legal_resources": {
+      "additionalProperties": false,
+      "properties": {
+        "privacy": {
+          "format": "uri",
+          "type": "string"
+        },
+        "refund": {
+          "format": "uri",
+          "type": "string"
+        },
+        "terms": {
+          "format": "uri",
+          "type": "string"
+        }
+      },
+      "required": [
+        "terms",
+        "privacy",
+        "refund"
+      ],
+      "type": "object"
+    },
+    "machine_onboarding": {
+      "format": "uri",
+      "type": "string"
+    },
+    "mcp_order_tool_exposed": {
+      "const": false,
+      "type": "boolean"
+    },
+    "order_policy": {
+      "type": "string"
+    },
+    "product_code": {
+      "enum": [
+        "MS-DEC-250",
+        "MS-ACT-25"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "product_code",
+    "customer_scope",
+    "input_requirement",
+    "order_policy",
+    "authoritative_order_protocol",
+    "machine_onboarding",
+    "legal_resources",
+    "mcp_order_tool_exposed",
+    "checkout_url_returned",
+    "boundaries"
+  ],
+  "type": "object"
+}

Changedget_synthetic_example2 fields changed

addedInput schema / properties / product_code / description

Added value: +"Product whose approved synthetic output preview should be returned."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "boundaries": {
+      "additionalProperties": false,
+      "description": "Permanent safety boundaries of the public MCP discovery server.",
+      "properties": {
+        "accepts_buyer_data": {
+          "const": false,
+          "type": "boolean"
+        },
+        "b2b_italy_only": {
+          "const": true,
+          "description": "Only Italian B2B buyers are in commercial scope.",
+          "type": "boolean"
+        },
+        "checkout_url_exposed": {
+          "const": false,
+          "type": "boolean"
+        },
+        "external_outreach_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "invoice_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "marketplace_publication_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "mode": {
+          "const": "public_read_only_discovery",
+          "description": "Public discovery mode; never an order-processing surface.",
+          "type": "string"
+        },
+        "order_tool_exposed": {
+          "const": false,
+          "type": "boolean"
+        },
+        "payment_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "persists_data": {
+          "const": false,
+          "type": "boolean"
+        },
+        "provider_call_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "provider_reference_loaded": {
+          "const": false,
+          "type": "boolean"
+        },
+        "sdi_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "wise_payout_enabled": {
+          "const": false,
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "mode",
+        "b2b_italy_only",
+        "accepts_buyer_data",
+        "persists_data",
+        "order_tool_exposed",
+        "checkout_url_exposed",
+        "provider_reference_loaded",
+        "provider_call_enabled",
+        "payment_enabled",
+        "invoice_enabled",
+        "sdi_enabled",
+        "wise_payout_enabled",
+        "external_outreach_enabled",
+        "marketplace_publication_enabled"
+      ],
+      "type": "object"
+    },
+    "canonical_example_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "example": {
+      "additionalProperties": {},
+      "description": "Approved synthetic product preview; never real buyer or company data.",
+      "type": "object"
+    }
+  },
+  "required": [
+    "example",
+    "canonical_example_url",
+    "boundaries"
+  ],
+  "type": "object"
+}

4 tool updatesJul 19, 2026
- First observedcheck_buyer_fit
- First observedget_product_catalog
- First observedget_purchase_requirements
- First observedget_synthetic_example

Related MCP Connectors

Italian B2B Lead Scoring, Ranking & JSON Decisions A
it.machinesignal
Score, rank and prioritize an existing Italian B2B lead list into explained JSON decisions.
CRM Marketing
61
Auditor IAOAuth
com.useauditoria.pilot
Audit B2B prospect lists before enrichment, CRM import or outreach.
CRM Data Platforms Testing & QA Tools
1
Lead Intelligence AOAuth
ai.saifs
Analyze and score leads to identify high-potential prospects and prioritize sales outreach.
CRM Customer Data Platforms Marketing
31
leadsmarts
app.leadsmarts
Qualify B2B leads: live-web research, Hot/Warm/Cold verdicts with evidence, and outreach drafts.
Search Marketing
1

Related MCP Servers

foundation-mcp-demo
CRM Data Platforms Security
kelvinDtran
F
license
Not graded
quality
C
maintenance
Enables an AI agent to turn a messy CRM account list into a ranked list of accounts to work, with every step authorized, scoped, rate limited, and replayable from an audit log.
Updated 13 days ago (2026-09-15 22:17 UTC)
-
B2B Lead Quality Scorer MCP
Email CRM
FoundryNet
A
license
Not graded
quality
F
maintenance
Validates email deliverability, assesses domain credibility, and scores B2B leads from A-F to help prioritize outreach, with batch processing and a free tier.
Updated 2 months ago (2026-08-11 06:22 UTC)
MIT
genpark-b2b-lead-waterfallofficial
Autonomous Agents CRM
alphaparkinc
F
license
Not graded
quality
B
maintenance
Enables autonomous B2B lead enrichment through a waterfall cascade and technographic stack verification, producing structured output dossiers for AI agents and enterprise pipelines.
Updated a month ago (2026-09-02 10:37 UTC)
8
-
Opportunity Radar
Product Management Research & Data
gcassata74
A
license
Not graded
quality
C
maintenance
Turns an unstructured business note into deterministic, explainable signals for revenue, automation, risk, urgency, and data, returning a score, priority, evidence, and a suggested next action. This lets an AI assistant assess and prioritize business opportunities through an auditable, locally computed tool.
Updated 17 days ago (2026-09-11 14:06 UTC)
MIT