Shibboleth
Providers using this tag (34)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Developing 1 Usable, with meaningful gaps to close
Thin 12 Limited public surface area
Emerging 21 Early or largely undocumented
APIs with this tag (188)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Strong 1 Solid coverage with minor gaps
Developing 31 Usable, with meaningful gaps to close
Thin 84 Limited public surface area
Emerging 72 Early or largely undocumented
Companies reaching this through an API (147)
These companies publish an API, specification or operation carrying “Shibboleth” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Show all 147 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 34 providers in the APIs.io catalog tagged Shibboleth, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Discoverability | 67.7 | 59.1 | +8.6 | 34 |
| Contract Quality | 24.5 | 18.6 | +5.9 | 34 |
| Developer Ergonomics | 26.3 | 24.5 | +1.8 | 34 |
| Contract Governance | 10.1 | 9.7 | +0.4 | 34 |
| Operational Transparency | 11.1 | 13.2 | -2.1 | 34 |
| Access Clarity | 19 | 30 | -11 | 34 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 0% | 18% | -18 |
| MCP server (first-party) | 0% | 16% | -16 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 12% | 13% | -1 |
| Security | 100% | 99% | +1 |
| Arazzo workflows | 0% | 1% | -1 |
| Governance rules | 41% | 36% | +5 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 University of Bonn 43.4
- 2 Washington University in St. Louis 37.3
- 3 Karlsruhe Institute of Technology 35.1
- 4 University of Ottawa 34
- 5 Tsinghua University 33.4
- 6 Shanghai Jiao Tong University 31.8
- 7 Michigan State University 31.3
- 8 Université de Montréal 30
- 9 Tokyo Institute of Technology 29.5
- 10 Indian Institute of Science Bangalore 28.6
- 1 Massey University 32.8
- 2 University of Ottawa 32.7
- 3 Shanghai Jiao Tong University 31.4
- 4 Politecnico di Milano 26.3
- 5 Humboldt-Universität zu Berlin 25.5
- 6 Universiti Putra Malaysia 25.3
- 7 Tsinghua University 25.2
- 8 Michigan State University 23.7
- 9 Universiti Sains Malaysia 23.5
- 10 Indian Institute of Science Bangalore 22.9
Coverage caveat. 26 of 34 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 14 November 2026, across 41591 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.