In-depth architectural comparison of the Nordic Data and Walmart Connect Advertising APIs MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Nordic Data
Developer Tools · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Walmart Connect Advertising APIs
Developer Tools · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Nordic Data if you need specialized Developer Tools tools running via a local process. Choose Walmart Connect Advertising APIs if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Nordic Data when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Nordic Data is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Walmart Connect Advertising APIs belongs to Developer Tools using local stdio subprocess. Select Nordic Data when you need capabilities focused on developer tools and Walmart Connect Advertising APIs when you require tools for developer tools.
Company data + geocoded address + industry stats + Wikidata (website, employees, CEO, ticker, logo)
fr_history
French company history timeline (name, activity, status, legal-form changes) from INSEE Sirene bitemporal data
list_endpoints
Discovery: list all read-only data endpoints in the underlying API (230+), with optional keyword filter
get_endpoint_schema
Discovery: full parameter + response schema for one endpoint, before calling it
call_endpoint
Discovery: execute a read-only request (GET/HEAD, plus three allowlisted POST screening queries) against any discovered endpoint
Walmart Connect Advertising APIs Tools (5)
list_endpoints
List operations from the bundled OpenAPI spec for an `ad_type`, with optional filters.
describe_endpoint
Return one operation plus the `components.schemas` reachable from it (its `$ref` closure), so request bodies and responses can be built without the full spec.
call_endpoint
Execute any Walmart Connect Ads API endpoint. Identify it by `operation_id`, or by raw `method` + `path`. Raw method+path also reaches alpha/beta/unpublished endpoints that are not in the bundled specs. The server handles RSA-SHA256 signing.
refresh_specs
Re-fetch the bundled OpenAPI specs from ReadMe's public api-registry into a user cache (`~/.cache/mcp-walmart-ads/specs/`) that takes precedence over the bundled copy.
download_display_snapshot
Download a display snapshot file (report or entity). Display snapshot URLs require authenticated requests, so this tool handles the signing automatically. Use the full download URL from the `details` field after polling a display snapshot to `done` status.
Walmart Connect Advertising APIs vs Sam's Club Sponsored Ads APIs