Skip to content

MCP servers › io.github.pugarte7 › spanish-top-tech-companies

MCP server · registry snapshot 2026-11-19 · last tested 2026-11-19

spanish-top-tech-companies MCP server

Registry name io.github.pugarte7/spanish-top-tech-companies

by pugarte7 · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

Tech salaries in Spain by role, region and company, and open job postings to apply to. — the publisher's description

5 of 5 record checks metRead-only · tools listed 2026-11-19version 1.21.0JavaScriptstreamable HTTP8 tools

Summary

io.github.pugarte7/spanish-top-tech-companies is a remote MCP server listed in the official MCP registry at version 1.21.0, under the namespace of the GitHub account pugarte7. Its linked repository, github.com/pugarte7/spanish-top-tech-companies, belongs to the same GitHub account. On 2026-11-19 ProtocolProbe connected to it in read-only mode and read its inventory: 8 tools, 0 resources and 0 prompts.

Record checks

5 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • #326 of 28,859 repositories by GitHub stars

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
8
Last tested
2026-11-19

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-19 (spanishtoptechcompanies.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.21.0).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-19
Mode
read-only (no tool calls)
Latest version
1.21.0, published 2026-11-18 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-14 (earliest version still in the registry; older removed versions would be earlier)
Version history
6 versions listed, 2026-11-14 to 2026-11-18; 6 in the 90 days before the 2026-11-19 snapshot.
Most recent 6 versions
  • 1.21.0 · 2026-11-18
  • 1.20.4 · 2026-11-16
  • 1.20.3 · 2026-11-16
  • 1.20.2 · 2026-11-16
  • 1.20.1 · 2026-11-14
  • 1.20.0 · 2026-11-14
(versions still listed in the registry only)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.20.4 (published 2026-11-16) → 1.21.0 (published 2026-11-18), between the registry lists of 2026-11-18 and 2026-11-19.

The publisher published no GitHub release note for version 1.21.0: the repository has no release tagged for it.

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.

What it is

What does this server offer?

Observed inventory
8tools
0resources
0prompts

None of its 8 tools are described as changing anything. For 8 the reading was uncertain, so no mark is shown.

  • salary_statson 5 other servers

    “What a job pays in Spain across companies: median base, the middle half (p25-p75), median total compensation (base plus bonus and stock) and the share of people at 60,000 EUR base or more, in euros p…”

    Publisher declares: read-only yes · open-world no

    4 inputs
    • rolestring“Role slug or name, e.g.”
    • regionstring“Spanish region code or name, e.g.”
    • yearsstring“Years of experience, as a number such as 6 or a bucket such as 5-7.”
    • contextstring“Why are you calling this tool?”
  • top_companieson 2 other servers

    “Every company the site's companies table lists for a selection, by median base, highest first, down to one salary; companies with fewer than 3 salaries in the selection come after the rest.”

    Publisher declares: read-only yes · open-world no

    6 inputs
    • rolestring“Role slug or name, e.g.”
    • regionstring“Spanish region code or name, e.g.”
    • yearsstring“Years of experience, as a number such as 6 or a bucket such as 5-7.”
    • searchstring“Filter companies by name.”
    • limitinteger
    • contextstring“Why are you calling this tool?”
  • company_salaries

    “One company in Spain, any the site lists, down to one salary: overall, and by role, region or experience wherever it has salaries.”

    Publisher declares: read-only yes · open-world no

    5 inputs, 1 required
    • namestringrequired“Company name, e.g.”
    • rolestring“Role slug or name, e.g.”
    • regionstring“Spanish region code or name, e.g.”
    • yearsstring“Years of experience, as a number such as 6 or a bucket such as 5-7.”
    • contextstring“Why are you calling this tool?”
  • “The values the other tools take, read from the data: every role slug with its name, every Spanish region code with its name and the experience buckets (0-1, 2-4, 5-7...) that have salaries, with the …”

    Publisher declares: read-only yes · open-world no

    1 input
    • contextstring“Why are you calling this tool?”
  • “Open postings at the companies on this site, from their public job boards (Greenhouse, Lever, Ashby, Workday and others), refreshed daily.”

    Publisher declares: read-only yes · open-world no

    11 inputs
    • querystring“Words to find in the title, company or location, or among the keywords read from the description: languages, frameworks, cloud, data and AI tools, security and…”
    • rolestring“A role from list_filters, e.g.”
    • regionstring“Spanish region code or name as in the salary tools (MD, Madrid, CT, Cataluña), spain, or remote.”
    • workplacestring“How the posting says the job is done.”
    • senioritystring“The level the title names: intern, junior, mid, senior, staff (staff or principal), lead, or head (head, director, VP, chief).”
    • yearsstring“The person's years of experience, a number such as 3, a range such as 3-4 or a bucket such as 2-4: leaves out postings whose description asks for more.”
    • companystring“Company name or slug, e.g.”
    • min_salary_eurinteger“Gross euros a year.”
    • excludearray“Job ids to leave out: postings already applied to, shown or turned down.”
    • limitinteger
    • contextstring“Why are you calling this tool?”
  • job_questions

    “The application form of one posting from find_jobs, read live from its board (Greenhouse, Lever, Ashby, Workable, Recruitee, Teamtailor, BambooHR, Pinpoint, Rippling, Bending Spoons and Eightfold; fo…”

    Publisher declares: read-only yes · open-world yes

    2 inputs, 1 required
    • idstringrequired“A job id from find_jobs, e.g.”
    • contextstring“Why are you calling this tool?”
  • report_application

    “After sending an application to a posting from find_jobs, or failing to, report the outcome: sent, uncertain (submitted, but the board neither confirmed nor clearly refused it), failed (with the reas…”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    8 inputs, 2 required
    • idstringrequired“The job id from find_jobs.”
    • statusstringrequired“sent: the board confirmed it, on the page or by email.”
    • reasonstring“Why it failed or is uncertain: captcha, login_required, form_error (a field was refused), upload_refused (the board would not take the CV file), submit_error (…”
    • browserstring“What you sent it with: built_in (your client's own browser), claude_in_chrome, playwright_mcp, other, or none.”
    • stepsarray“What it took beyond filling the form, every one that applies: set_up_browser (you had to add a browser tool), switched_browser (the first tool failed and anoth…”
    • attemptsinteger“How many times you submitted.”
    • notesstring“In a sentence or two, what you had to work out that these tools did not tell you: the tool or trick that worked, what the board did.”
    • contextstring“Why are you calling this tool?”
  • application_guide

    “The procedure for applying on someone's behalf with find_jobs and job_questions: the state document to keep for them (profile, recurring answers, search preferences, applications), the rules, how an …”

    Publisher declares: read-only yes · open-world no

    2 inputs
    • clientstring“The client you run in, e.g.”
    • contextstring“Why are you calling this tool?”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-19.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
95% of 39
Tools with a description
100% of 8
Typical description length
560 characters

The tool set

Counted from the listing

Tools
8
Size of the list
about 3,554 tokens for an agent to load (characters ÷ 4)
Naming
8 of 8 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 8 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-19 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://spanishtoptechcompanies.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "spanish-top-tech-companies": {
      "url": "https://spanishtoptechcompanies.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "spanish-top-tech-companies": {
      "type": "http",
      "url": "https://spanishtoptechcompanies.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"spanish-top-tech-companies","type":"http","url":"https://spanishtoptechcompanies.com/mcp"}'
Claude Code
claude mcp add --transport http spanish-top-tech-companies https://spanishtoptechcompanies.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "spanish-top-tech-companies": {
      "type": "streamableHttp",
      "url": "https://spanishtoptechcompanies.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "spanish-top-tech-companies": {
      "httpUrl": "https://spanishtoptechcompanies.com/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.spanish-top-tech-companies]
url = "https://spanishtoptechcompanies.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "spanish-top-tech-companies": {
      "url": "https://spanishtoptechcompanies.com/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://spanishtoptechcompanies.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint spanishtoptechcompanies.com/mcpSession openedmatchesour test · 2026-11-19
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-19
Repository github.com/pugarte7/spanish-top-tech-companiesOpens publiclymatchesapi.github.com · 2026-11-19

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.pugarte7
GitHub owner
a personal account (pugarte7)
Repository
github.com/pugarte7/spanish-top-tech-companies
Stars
604
Repository age
31–90 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-15.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Tool list changes

Our reads compared · no tool called

Hosted endpoint spanishtoptechcompanies.com/mcp

No change in the tool list across 3 reads (2026-11-15 to 2026-11-19; versions 1.20.1 to 1.21.0).

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-19 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • #326 of 28,859 repositories by GitHub stars
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-15). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.pugarte7/spanish-top-tech-companies

Answered from the data above

Who publishes io.github.pugarte7/spanish-top-tech-companies?

The registry ties the namespace io.github.pugarte7 to the GitHub account pugarte7; only its owner can publish under it. Its linked repository, github.com/pugarte7/spanish-top-tech-companies, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.pugarte7/spanish-top-tech-companies safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.pugarte7/spanish-top-tech-companies need an API key or sign-in?

It opened a session without any credential on 2026-11-19. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.pugarte7/spanish-top-tech-companies been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Does io.github.pugarte7/spanish-top-tech-companies publish a security policy?

Yes: its repository has a public security policy (github.com/pugarte7/spanish-top-tech-companies/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of io.github.pugarte7/spanish-top-tech-companies?

In github.com/pugarte7/spanish-top-tech-companies, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (no operator permission)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-19
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-19, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 800 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 8 tools, 0 resources, 0 prompts.
  4. 3,484 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-19; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-19
Hosting type
registry · 2026-11-19
MCP capability
tools
our test · 2026-11-19
Transport
streamable HTTP
registry · 2026-11-19
Required credentials
none declared
registry · 2026-11-19 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-19
Lifecycle status
registry · 2026-11-19
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 31–90 days · stars: 100–999
api.github.com · 2026-11-19
Maintenance
api.github.com · 2026-11-19
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-19

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.pugarte7/spanish-top-tech-companies: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.pugarte7/spanish-top-tech-companies

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 5 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.pugarte7/spanish-top-tech-companies)](https://protocolprobe.com/mcp/servers/io.github.pugarte7/spanish-top-tech-companies)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology